Closed
Bug 492808
Opened 15 years ago
Closed 15 years ago
Forced clobber message is misleading
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: catlee)
Details
Attachments
(2 files, 1 obsolete file)
1.20 KB,
patch
|
nthomas
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
1.35 KB,
patch
|
nthomas
:
review+
catlee
:
checked-in+
|
Details | Diff | Splinter Review |
If a slave's build directory is empty, and the clobber server returns a non-null value for the clobber date, the current clobberer script will treat that as a trigger to force a clobber. This results in a message "Server is forcing a clobber", which various other tools pick up on. The problem is that 99% of the time, the build directory has been clobbered by some other build needing space. Also, saying that the server is forcing a clobber is misleading because the build directory is already clobbered. We should fix the clobberer script so it doesn't warn about this common case. We should also indicate when a clobber build is occurring.
Assignee | ||
Comment 1•15 years ago
|
||
Attachment #377218 -
Flags: review?(nthomas)
Assignee | ||
Comment 2•15 years ago
|
||
Attachment #377219 -
Flags: review?(nthomas)
Assignee | ||
Updated•15 years ago
|
Attachment #377219 -
Flags: review?(bhearsum)
Updated•15 years ago
|
Attachment #377219 -
Flags: review?(bhearsum) → review+
Comment 3•15 years ago
|
||
Comment on attachment 377219 [details] [diff] [review] Detect if we have no build directory, and set the purge_clobber property accordingly Had a chance to give this a spin in staging ?
Attachment #377219 -
Flags: review?(nthomas) → review+
Comment 4•15 years ago
|
||
Comment on attachment 377218 [details] [diff] [review] Only do a server forced clobber if we know what our last clobber time was Looks fine.
Attachment #377218 -
Flags: review?(nthomas) → review+
Comment 5•15 years ago
|
||
Sounds like this is yours, Chris.
Assignee: nobody → catlee
Status: NEW → ASSIGNED
Assignee | ||
Updated•15 years ago
|
Attachment #377218 -
Flags: checked‑in+
Assignee | ||
Comment 6•15 years ago
|
||
Comment on attachment 377218 [details] [diff] [review] Only do a server forced clobber if we know what our last clobber time was changeset: 282:34afe709615b
Assignee | ||
Comment 7•15 years ago
|
||
Attachment #377219 -
Attachment is obsolete: true
Attachment #381370 -
Flags: review?(nthomas)
Comment 8•15 years ago
|
||
Comment on attachment 381370 [details] [diff] [review] Detect if our clobber time was None, and set purged_clobber accordingly Looks like the various states are exclusive, so that the elif is fine. r+
Attachment #381370 -
Flags: review?(nthomas) → review+
Assignee | ||
Comment 9•15 years ago
|
||
Comment on attachment 381370 [details] [diff] [review] Detect if our clobber time was None, and set purged_clobber accordingly changeset: 331:4ce9333c706b
Attachment #381370 -
Flags: checked‑in+
Assignee | ||
Updated•15 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•