Intermittent Exception: Missing fetch job for toolchain-toolchain-macosx64-x64-libotr: linux64-llvm-dsymutil
Categories
(Thunderbird :: Build Config, defect, P5)
Tracking
(Not tracked)
People
(Reporter: intermittent-bug-filer, Unassigned)
References
Details
(Keywords: intermittent-failure)
Filed by: ishikawa [at] yk.rim.or.jp
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=351226309&repo=try-comm-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/K9SVj20-TcyyZG45j3FCtA/runs/0/artifacts/public/logs/live_backing.log
This is beyond control of an individual submitter.
I don't see this all the time, so presumably this is an intermittent failure?
(I can't see why some submissions see this and others don't.)
Comment 1•4 years ago
|
||
I think this is permanent.
It does not matter whether I mention macosx64 in the target or not.
The macosx64 tool or something fails to be fetched and aborts the job.
Updated•4 years ago
|
| Comment hidden (Intermittent Failures Robot) |
Comment 6•4 years ago
|
||
I suspect you need to rebase your local copy of comm-central before pushing to try-comm-central. Try builds by default will always build with the latest revision of mozilla-central, which may not work if you have not updated in a few days.
Comment 7•4 years ago
|
||
I(In reply to Rob Lemley [:rjl] from comment #6)
I suspect you need to rebase your local copy of comm-central before pushing to try-comm-central. Try builds by default will always build with the latest revision of mozilla-central, which may not work if you have not updated in a few days.
I see.
This is a situation where one becomes a bit suspicious of the latest M-C/C-C combination due to the build failures and thus
hold on updating for a day or two, which makes the situation worse.
Since I test binary locally, the local build time is really wasted if build fails after update and thus
I tend to keep the local C-C NOT updated when a serious debug work goes on.
(Compiling takes close to 1.5 - 2 hours depending on other work I do on my computer.)
I will bite the bullet and update my M-C/C-C.
TIA
Comment 8•4 years ago
|
||
(In reply to Rob Lemley [:rjl] from comment #6)
I suspect you need to rebase your local copy of comm-central before pushing to try-comm-central. Try builds by default will always build with the latest revision of mozilla-central, which may not work if you have not updated in a few days.
Thanks. After refershing M-C/C-C, it works again.
https://treeherder.mozilla.org/jobs?repo=try-comm-central&revision=e52acff412f8a02be4c261e67e87ebaad9ad522a
The strange issue of not being able to build/test TB on try server farm in mid-August made me very cautious here, and it backfired.
Description
•