Intermittent timeout in /html/browsers/browsing-the-web/navigating-across-documents/014.html and /html/browsers/browsing-the-web/navigating-across-documents/013.html and /html/browsers/browsing-the-web/navigating-across-documents/015.html

[jdm]

This looks like an issue caused by interleaving output?

  ▶ TIMEOUT [expected OK] /html/browsers/browsing-the-web/navigating-across-documents/014.html
  │ 
  │ ERROR:script::dom::bindings::error: Error at :0:1 parent.events is undefinedALERT: RESULT: ["/html/browsers/browsing-the-web/navigating-across-documents/014.html",0,null,null,[[" Link with javascript onclick form submission script order ",1,"assert_array_equals: lengths differ, expected 2 got 1","onload<@http://web-platform.test:8000/html/browsers/browsing-the-web/navigating-across-documents/014.html:9:3\nTest.prototype.step@http://web-platform.test:8000/resources/testharness.js:1402:20\nTest.prototype.step_func/<@http://web-platform.test:8000/resources/testharness.js:1426:20\n"]]]
  └ 

[jdm]

The JS error uses error!, which goes through env_logger which uses writeln! on stderr. The ALERT: comes from console.log, which uses println! and therefore stdout. I'm not sure if there's a way around this.

[splav]

Why just not to redirect stderr and stdout to different files?

[jdm]

That would make us lose terminal output, right? That's a pretty big deal. I think we could get around this by making console.log also take the stderr lock.