59 bytes, text/x-review-board-request
Here is a link to Orange Factor: https://brasstacks.mozilla.com/orangefactor/index.html?display=Bug&bugid=1414514 :ahal, I have been doing a lot of testing on try on windows 10 this weekend (testing mochitest without marionette I see this often, not with marionette like the above error) and this error has shown up often for me- any thoughts on why this might be happening?
we should fix up the code to print req.status: http://searchfox.org/mozilla-central/source/testing/mochitest/manifestLibrary.js#42 this would at least give up a place to start- I am not sure if the error is in the in-browser bits, maybe the browser is having issues with loading network due to some condition, or maybe the webserver serving http://localhost is having problems.
some additional logs with this from try runs: https://public-artifacts.taskcluster.net/DXjUZcTGTiGovZrwQ0LsCA/0/public/logs/live_backing.log https://public-artifacts.taskcluster.net/a5ug4PWvQJmR7gMSwoHKMg/0/public/logs/live_backing.log
I love how the error message has the wrong filename hardcoded. I'm not sure why this is happening either, but agree we should improve the error message. I can add this sometime soon, I'll leave the needinfo for now to remind myself.
Comment on attachment 8926048 [details] Bug 1414514 - [mochitest] Dump http status when failing to load test manifest, https://reviewboard.mozilla.org/r/197278/#review202432 nice and simple
Attachment #8926048 - Flags: review?(jmaher) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/autoland/rev/9cc431483c61 [mochitest] Dump http status when failing to load test manifest, r=jmaher
Just realized this changes the failure signature. Once we figure out the HTTP code, lets also add that to the summary.
Summary: Intermittent GECKO(6976) | TEST-UNEXPECTED-FAIL: setup.js | error loading http://mochi.test:8888/tests.json → Intermittent GECKO(6976) | TEST-UNEXPECTED-FAIL: manifestLibrary.js | error loading http://mochi.test:8888/tests.json
Oops, forgot to add [leave-open]. The single bug starred here doesn't have this change. I wonder if a new bug ended up being opened due to this being resolved :/.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → RESOLVED
Closed: 2 years ago → 2 years ago
Resolution: --- → INCOMPLETE
Component: Mochitest Chrome → Mochitest
You need to log in before you can comment on or make changes to this bug.