Intermittent timeout in /html/browsers/history/the-location-interface/location-protocol-setter-non-broken.html

[jdm]

It's not clear to me where this error originates from. It's also not clear if this is just an instance of the test harness failing to recognize the process aborting, given that the original build log had a huge cascade of panics following this one.

  ▶ TIMEOUT [expected CRASH] /html/browsers/history/the-location-interface/location-protocol-setter-non-broken.html
  │ 
  │ VMware, Inc.
  │ Gallium 0.4 on softpipe
  │ 3.3 (Core Profile) Mesa 12.0.1
  │ called `Result::unwrap()` on an `Err` value: Serde(Custom("Invalid value: invalid domain character")) (thread <unnamed>, at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libcore/result.rs:868)
  │ stack backtrace:
  │    0:     0x7fd4eb60fc9d - backtrace::backtrace::trace::h976012eed768c7ff
  │    1:     0x7fd4eb610182 - backtrace::capture::Backtrace::new::hb5a725a088a2a2fc
  │    2:     0x7fd4eb335447 - servo::main::{{closure}}::h039ba3c803113243
  │    3:     0x7fd4ed198988 - std::panicking::rust_panic_with_hook
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:556
  │    4:     0x7fd4ed198854 - std::panicking::begin_panic<collections::string::String>
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:517
  │    5:     0x7fd4ed198779 - std::panicking::begin_panic_fmt
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:501
  │    6:     0x7fd4ed198707 - std::panicking::rust_begin_panic
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/panicking.rs:477
  │    7:     0x7fd4ed1c5ecd - core::panicking::panic_fmt
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libcore/panicking.rs:69
  │    8:     0x7fd4eb398332 - core::result::unwrap_failed::hf8687c4d6fe28078
  │    9:     0x7fd4eb35b331 - ipc_channel::router::RouterProxy::route_ipc_receiver_to_mpsc_sender::{{closure}}::h3ce7b5c4a86d1ea3
  │   10:     0x7fd4ed0b3a90 - ipc_channel::router::RouterProxy::new::{{closure}}::h8289a70e1d7c4967
  │   11:     0x7fd4ed0ad1ec - std::panicking::try::do_call::h5bf0a54fba863c1f
  │   12:     0x7fd4ed19f8ca - panic_unwind::__rust_maybe_catch_panic
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libpanic_unwind/lib.rs:98
  │   13:     0x7fd4ed0b0516 - <F as alloc::boxed::FnBox<A>>::call_box::h3d5aa4284b6a48ab
  │   14:     0x7fd4ed197614 - alloc::boxed::{{impl}}::call_once<(),()>
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/liballoc/boxed.rs:623
  │                          - std::sys_common::thread::start_thread
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/sys_common/thread.rs:21
  │                          - std::sys::imp::thread::{{impl}}::new::thread_start
  │                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/sys/unix/thread.rs:84
  │   15:     0x7fd4e9203183 - start_thread
  │   16:     0x7fd4e8d1a37c - clone
  │   17:                0x0 - <unknown>

[asajeffrey]

Tracked this down to servo/rust-url#278 cc @SimonSapin

[asajeffrey]

It's intermittent because if the panic occurs while the other tests are still running, they produce a TIMEOUT.

[jdm]

I have caught this in rr; it no longer panics since #15618. Like #15239, this test loads six iframes, and it times out before it gets a chance to run the first onload event.