Closed
Bug 663077
Opened 14 years ago
Closed 14 years ago
Buildbot does not calculate build revision when only change hash is used to trigger a build
Categories
(Tamarin Graveyard :: Build Config, defect)
Tamarin Graveyard
Build Config
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: brbaker, Unassigned)
Details
(Whiteboard: buildbot)
Attachments
(1 file)
|
1.42 KB,
patch
|
jsudduth
:
review+
|
Details | Diff | Splinter Review |
If you request a sandbox build only using the change hash, buildbot will fail in the smoke phase when it tries to confirm the revision of the deployed avmshell on remote machines (linux-arm, android, linux-mips). The all/util-calculate-change.sh script currently does not handle only being passed the change hash.
| Reporter | ||
Comment 1•14 years ago
|
||
Comment on attachment 538232 [details] [diff] [review]
Calculate change info bash on hash
This is sort of naive since it assumes that anything passed in that has a length of 12 is a revision hash. This will start to fail once tamarin reaches change number 100,000,000,000, but we should be ok for a little while.
Comment 2•14 years ago
|
||
Comment on attachment 538232 [details] [diff] [review]
Calculate change info bash on hash
Looks good - might want to fix the typo in the comment ('lenght').
Attachment #538232 -
Flags: review?(jsudduth) → review+
Comment 3•14 years ago
|
||
changeset: 6385:50081aa3683b
user: Brent Baker <brbaker@adobe.com>
summary: Bug 663077 - Buildbot does not calculate build revision when only change hash is used to trigger a build (r=jsudduth)
http://hg.mozilla.org/tamarin-redux/rev/50081aa3683b
| Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Reporter | ||
Updated•14 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•