Closed Bug 1050898 Opened 11 years ago Closed 11 years ago

Linux B2G desktop builds hitting frequent upload failures across multiple trees

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86
Linux
task
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: RyanVM, Unassigned)

Details

https://tbpl.mozilla.org/php/getParsedLog.php?id=45548764&tree=Mozilla-B2g28-v1.3 b2g_mozilla-b2g28_v1_3_linux64_gecko build on 2014-08-08 08:28:49 PDT for push ac685e277c7c slave: bld-linux64-spot-060 INFO: mock_mozilla.py version 1.0.3 starting... State Changed: init plugins INFO: selinux disabled State Changed: start State Changed: lock buildroot State Changed: shell retry: Calling <function run_with_timeout at 0x7f7304376848> with args: (['make', 'upload'], 2460, None, None, False, True), kwargs: {}, attempt #1 Executing: ['make', 'upload'] make[1]: Entering directory `/builds/slave/m-b28_13-l64_g-000000000000000/build/obj-firefox/b2g/installer' mkdir -p `dirname '../../dist//b2g-28.0.en-US.linux-x86_64.checksums'` CHECKSUM FILE START 3ffefab287525efba1af7936ea6c862a884c3917497fe30f50ee4b32e4aeeb66086ee945b12a71b6d70616d9e14be5b3e9db3028b45917292f8d794ed29f02da sha512 81669476 b2g-28.0.en-US.linux-x86_64.tar.bz2 4ca935dc82ca09500581bd5d28bb2708 md5 81669476 b2g-28.0.en-US.linux-x86_64.tar.bz2 de9e85e98eea8f18312b7853e7a962c3dcf8c170 sha1 81669476 b2g-28.0.en-US.linux-x86_64.tar.bz2 5ba7ac4c3fb8497a80c0793027ae147f9e60c9588d6f18790851a583287096bdaa252c9eb6064204d1c0024e76236fb83f51cb05e90c8b726b3bd5a02fb41e05 sha512 107425514 b2g-28.0.en-US.linux-x86_64.tests.zip c5e5520de43fb8d3bceb652c914b232b md5 107425514 b2g-28.0.en-US.linux-x86_64.tests.zip 3a19be4016bc7740364bc68e893e1d3ed91c1ea9 sha1 107425514 b2g-28.0.en-US.linux-x86_64.tests.zip 66e7b7459dd81aafac256ddc16698ffef87c83fe5e0a4d3a3f04508ecde86301872451a0e230d0329ef8203d5880d15925d22d50a60c7ef4155e1745b1b4faf5 sha512 25779984 b2g-28.0.en-US.linux-x86_64.crashreporter-symbols.zip 146092f74e69d068b1b5305254c27893 md5 25779984 b2g-28.0.en-US.linux-x86_64.crashreporter-symbols.zip 9118c6e5a458e2546a2cc110b60e31c96f39fed4 sha1 25779984 b2g-28.0.en-US.linux-x86_64.crashreporter-symbols.zip 4801694616e9e20ed86e06c277583cde7348361bbf14d1607d078072cf170ca720d7f0cd960dc7328209daeead28ff8aefdcc430b4204ee00bf893a6e518d6c5 sha512 83 b2g-28.0.en-US.linux-x86_64.txt 833fe6219fd1a860cc915efdf9b018dd md5 83 b2g-28.0.en-US.linux-x86_64.txt 48fd1d3181a364aa9cf791bdf17733b4a87ee1a1 sha1 83 b2g-28.0.en-US.linux-x86_64.txt c47ee3d257eff4cb9f7e4eb3566f6ac66840b7984dd448470a165b00d5144a03c88ddbfb9d36c1aa96179d5d0ad69ae241d3ce9c65f80c9171c98c04bd78e5d9 sha512 818 b2g-28.0.en-US.linux-x86_64.json d1eb059a3453deddf3e06bde305b2be9 md5 818 b2g-28.0.en-US.linux-x86_64.json 453bf37d6fc27551f72628c4848c1149133b1c2d sha1 818 b2g-28.0.en-US.linux-x86_64.json CHECKSUM FILE END /builds/slave/m-b28_13-l64_g-000000000000000/build/obj-firefox/_virtualenv/bin/python /builds/slave/m-b28_13-l64_g-000000000000000/build/build/upload.py --base-path ../../dist \ '../../dist/b2g-28.0.en-US.linux-x86_64.tar.bz2' '../../dist/b2g-28.0.en-US.linux-x86_64.tests.zip' '../../dist/b2g-28.0.en-US.linux-x86_64.crashreporter-symbols.zip' '../../dist//b2g-28.0.en-US.linux-x86_64.txt' '../../dist//b2g-28.0.en-US.linux-x86_64.json' \ '../../dist//b2g-28.0.en-US.linux-x86_64.checksums' WARNING: Timeout (2460) exceeded, killing process 10685 make[1]: *** [upload] Terminated make: *** [upload] Terminated
[16:03:19] Callek|Buildduty RyanVM|sheriffduty: so whats the current take on Bug 1050898 a one-off that I can close as self-healed [16:03:26] Callek|Buildduty or ongoing just not-frequent, or other [16:03:34] RyanVM|sheriffduty appears to have cleared up on its own [16:03:51] Callek|Buildduty ok, I'm closing it for now then, feel free to reopen or file anew if it re-appers
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.