Closed
Bug 1156025
Opened 9 years ago
Closed 9 years ago
Treeherder try push stuck again
Categories
(Tree Management :: Treeherder, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: bholley, Unassigned)
Details
Another instance of bug 1105873. All of these have happened the same way - I do a try push, and then I very quickly load the URL it gives me. If I do it quickly enough, the push isn't ready yet, and it seems to _stay_ in this pending state, possibly as the result of me having requested it so early? https://treeherder.mozilla.org/#/jobs?repo=try&revision=c8b7892dd4e
Reporter | ||
Updated•9 years ago
|
Flags: needinfo?(emorley)
Comment 1•9 years ago
|
||
The URL in comment 0 is missing the last character - did it get missed off when copy pasting from the console? The correct URL is: https://treeherder.mozilla.org/#/jobs?repo=try&revision=c8b7892dd4e7 Unfortunately it seems that hgweb matches against partial SHAs (which I guess makes sense, since it's still a valid revset) so following the hgweb link in the "waiting for push" page shows results, rather than a 404 which would make the typo clearer. I guess we could hardcode an expected SHA length in the Treeherder ui.
Flags: needinfo?(emorley)
Reporter | ||
Comment 2•9 years ago
|
||
Facepalm - Thanks Ed! Sorry for the noise.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Comment 3•9 years ago
|
||
I've filed bug 1157699 to make this clearer to the user (ie: if the SHA isn't the expected length, so we know it won't match anything in the DB, then show an error).
You need to log in
before you can comment on or make changes to this bug.
Description
•