Closed
Bug 1231066
Opened 10 years ago
Closed 10 years ago
Clobber silently failing
Categories
(Testing Graveyard :: Sisyphus, defect)
Testing Graveyard
Sisyphus
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: cbook, Assigned: cbook)
Details
Attachments
(1 file)
729 bytes,
patch
|
bc
:
review-
|
Details | Diff | Splinter Review |
In Bug 1019626 we enabled always clobber to prevent depends builds issues
and then we noticed build failures due to a missing clobber and added autoclobber=1 in Bug 1058612
what we missed here is that if clobber had worked like expected Bug 1019626 we would had never to file Bug 1058612, because if we clobber always why:
1. Enable autoclobbering so we don't fail a build just because a clobber is required.
was needed :)
i found out that this is because need to be changed from
- buildsteps = "clobber checkout build"
+ buildsteps = "checkout clobber build"
to make clobber working again
Attachment #8696609 -
Flags: review?(bob)
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → cbook
Comment 1•10 years ago
|
||
I don't understand how this would work. The worker.py calls builder.sh http://hg.mozilla.org/automation/sisyphus/file/tip/bin/builder.sh#l92 which doesn't process the build commands in order. Instead it checks for clean, clobber, checkout then build in that order regardless of the order they are specified on the command line.
clobber checkout build should be identical to checkout clobber build
Assignee | ||
Comment 2•10 years ago
|
||
invalid per discussion on irc
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Updated•10 years ago
|
Attachment #8696609 -
Flags: review?(bob) → review-
Updated•7 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•