Closed
Bug 1101059
Opened 11 years ago
Closed 11 years ago
Clobber failing with "Couldn't clobber properly, bailing out", on bld-lion-r5-051
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: dholbert, Assigned: mrrrgn)
References
()
Details
Attachments
(1 file)
|
1.41 KB,
patch
|
coop
:
review+
mrrrgn
:
checked-in+
|
Details | Diff | Splinter Review |
Filing this bug for a busted build job, with the error being "Couldn't clobber properly, bailing out".
Log info:
{
builder: mozilla-inbound-macosx64-debug
slave: bld-lion-r5-051
starttime: 1416331850.64
results: failure (2)
buildid: 20141118092826
builduid: bb16079626b64c549064a2cc6e520872
revision: 156f8e3bc89d1385510a01335ffe526eb0005728
}
Log snippet:
{
09:30:57 INFO - ##### Running clobber step.
09:30:57 INFO - #####
09:30:57 INFO - Running main action method: clobber
09:30:57 INFO - retry: Calling <bound method FxDesktopBuild.run_command of <__main__.FxDesktopBuild object at 0x1010a7890>> with args: [['/builds/slave/m-in-osx64-d-00000000000000000/scripts/external_tools/clobberer.py', '-s', 'scripts', '-s', 'logs', '-s', 'buildprops.json', '-s', 'token', '-t', '168', 'https://api.pub.build.mozilla.org/clobberer/lastclobber', 'mozilla-inbound', 'OS X 10.7 64-bit mozilla-inbound leak test build', 'm-in-osx64-d-00000000000000000', 'bld-lion-r5-051', 'http://buildbot-master84.srv.releng.scl3.mozilla.com:8001/']], kwargs: {'error_list': [{'substr': 'Error contacting server', 'explanation': 'Error contacting server for clobberer information.', 'level': 'error'}], 'cwd': '/builds/slave'}, attempt #1
09:30:57 INFO - Running command: ['/builds/slave/m-in-osx64-d-00000000000000000/scripts/external_tools/clobberer.py', '-s', 'scripts', '-s', 'logs', '-s', 'buildprops.json', '-s', 'token', '-t', '168', 'https://api.pub.build.mozilla.org/clobberer/lastclobber', 'mozilla-inbound', 'OS X 10.7 64-bit mozilla-inbound leak test build', 'm-in-osx64-d-00000000000000000', 'bld-lion-r5-051', 'http://buildbot-master84.srv.releng.scl3.mozilla.com:8001/'] in /builds/slave
09:30:57 INFO - Copy/paste: /builds/slave/m-in-osx64-d-00000000000000000/scripts/external_tools/clobberer.py -s scripts -s logs -s buildprops.json -s token -t 168 https://api.pub.build.mozilla.org/clobberer/lastclobber mozilla-inbound "OS X 10.7 64-bit mozilla-inbound leak test build" m-in-osx64-d-00000000000000000 bld-lion-r5-051 http://buildbot-master84.srv.releng.scl3.mozilla.com:8001/
09:30:59 INFO - Checking clobber URL: https://api.pub.build.mozilla.org/clobberer/lastclobber?master=http%3A%2F%2Fbuildbot-master84.srv.releng.scl3.mozilla.com%3A8001%2F&slave=bld-lion-r5-051&builddir=m-in-osx64-d-00000000000000000&branch=mozilla-inbound&buildername=OS+X+10.7+64-bit+mozilla-inbound+leak+test+build
09:30:59 INFO - m-in-osx64-d-00000000000000000:Our last clobber date: 2014-11-03 22:09:46
09:30:59 INFO - m-in-osx64-d-00000000000000000:Server clobber date: 2014-11-18 08:30:50
09:30:59 INFO - m-in-osx64-d-00000000000000000:Server is forcing a clobber, initiated by cbook@mozilla.com
09:30:59 INFO - m-in-osx64-d-00000000000000000:Clobbering...
09:30:59 INFO - Removing build/
09:30:59 INFO - Couldn't clobber properly, bailing out.
09:30:59 ERROR - Return code: 1
09:30:59 INFO - retry: Failed, sleeping 60 seconds before retrying
}
(It retries twice more, with the same results.)
| Comment hidden (Legacy TBPL/Treeherder Robot) |
| Reporter | ||
Updated•11 years ago
|
Blocks: bld-lion-r5-051
| Reporter | ||
Comment 2•11 years ago
|
||
| Reporter | ||
Updated•11 years ago
|
OS: All → Mac OS X
| Assignee | ||
Comment 3•11 years ago
|
||
This one may end up impossible to reproduce. I just logged into the same machine and tried to replicate the conditions with no success.... One possibility is that there was a permission error or an unreadable character in some filename. The best way to approach this will likely be to add more specific error messages to the clobberer client.
Here's my attempt to reproduce on the same builder: https://pastebin.mozilla.org/7367193
| Assignee | ||
Updated•11 years ago
|
Assignee: nobody → winter2718
| Assignee | ||
Comment 4•11 years ago
|
||
Attachment #8524768 -
Flags: review?(coop)
| Assignee | ||
Comment 5•11 years ago
|
||
My proposal here is to put in this patch with more detailed messages, then close this bug. When an error happens next it will be much easier to figure out what happened. As it stands, I don't think I have enough to go on.
Comment 6•11 years ago
|
||
Comment on attachment 8524768 [details] [diff] [review]
clobberer.errors.diff
Review of attachment 8524768 [details] [diff] [review]:
-----------------------------------------------------------------
(In reply to Morgan Phillips [:mrrrgn] from comment #5)
> My proposal here is to put in this patch with more detailed messages, then
> close this bug. When an error happens next it will be much easier to figure
> out what happened. As it stands, I don't think I have enough to go on.
Yes, it's also possible that there is simply something wrong with this particular machine. More info is good.
Attachment #8524768 -
Flags: review?(coop) → review+
| Assignee | ||
Updated•11 years ago
|
Attachment #8524768 -
Flags: checked-in+
| Assignee | ||
Comment 7•11 years ago
|
||
Marking as resolved incomplete. The next time a problem happens we should have detailed errors which will allow us to debug properly and fix the issue without wasting lots of dev time trying to recreate the problem.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Updated•7 years ago
|
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•