getting rust backtrace while building c-c linux64 nightly

NEW
Unassigned

Status

defect
5 months ago
5 months ago

People

(Reporter: ewong, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Reporter

Description

5 months ago

While finally we have something building on c-c, it's still not
completing due to the following backtrace:

Since this is rust-related, will need to ask/look around:

19:33.01 [style 0.0.1] cargo:rerun-if-changed=/builds/worker/c-cen-t-lnx64-ntly/build/obj-x86_64-pc-linux-gnu/dist/include/mozilla/Services.h
19:33.01 [style 0.0.1] cargo:rerun-if-changed=/builds/worker/c-cen-t-lnx64-ntly/build/obj-x86_64-pc-linux-gnu/dist/include/js/Proxy.h
19:33.01 [style 0.0.1] cargo:rerun-if-changed=/builds/worker/c-cen-t-lnx64-ntly/build/obj-x86_64-pc-linux-gnu/dist/include/mozilla/StyleComplexColor.h
19:33.01 [style 0.0.1] cargo:rerun-if-changed=/builds/worker/c-cen-t-lnx64-ntly/build/obj-x86_64-pc-linux-gnu/dist/include/LayoutConstants.h
19:33.01 thread 'main' panicked at 'stack backtrace:
19:33.11 0: 0x7f5c0187109f - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::hab66bb8ff7088f29
19:33.11 at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
19:33.11 1: 0x7f5c0187f0d7 - std::sys_common::backtrace::print::h56719ed580ab1bba
19:33.11 at libstd/sys_common/backtrace.rs:71
19:33.11 at libstd/sys_common/backtrace.rs:59
19:33.11 2: 0x7f5c0187759f - std::panicking::default_hook::{{closure}}::hf8d811a2c97e4b3a
19:33.11 at libstd/panicking.rs:211
19:33.11 3: 0x7f5c01877304 - std::panicking::default_hook::hc6e051251a5e6b4e
19:33.11 at libstd/panicking.rs:227
19:33.11 4: 0x7f5c01877c7e - std::panicking::rust_panic_with_hook::h71214e7ce0f7ac01
19:33.11 at libstd/panicking.rs:476
19:33.11 5: 0x7f5c01877821 - std::panicking::continue_panic_fmt::ha8b8442f4ea9bcac
19:33.11 at libstd/panicking.rs:390
19:33.11 6: 0x7f5c0187776e - std::panicking::begin_panic_fmt::h11692d2d479bd3e6
19:33.11 at libstd/panicking.rs:345
19:33.11 7: 0x7f5c0186d9e2 - std::io::stdio::_print::hc75f748cc7055f8a
19:33.11 at libstd/io/stdio.rs:700
19:33.11 at libstd/io/stdio.rs:709
19:33.11 8: 0x7f5c011ffc39 - cargo::core::compiler::job_queue::JobQueue::drain_the_queue::h3a28bb380db95beb
19:33.11 9: 0x7f5c01155d7d - crossbeam_utils::thread::scope::h2e7e3e6534c1a88a
19:33.11 10: 0x7f5c011fdcfd - cargo::core::compiler::job_queue::JobQueue::execute::hd0654bfccaae0347
19:33.11 11: 0x7f5c0136823a - cargo::core::compiler::context::Context::compile::h815063c119aac638
19:33.12 12: 0x7f5c011365c3 - cargo::ops::cargo_compile::compile_ws::h69e6594fd737c309
19:33.12 13: 0x7f5c01132c98 - cargo::ops::cargo_compile::compile::h47ce9d42b2b3efee
19:33.12 14: 0x7f5c010bba45 - cargo::commands::rustc::exec::ha230f43d1aaf6991
19:33.12 15: 0x7f5c0108c430 - cargo::cli::main::h8316c8e46496f65f
19:33.12 16: 0x7f5c010bbd9f - cargo::main::hfe4c7eca238e1ad7
19:33.12 17: 0x7f5c010b3eb2 - std::rt::lang_start::{{closure}}::h24676f7d356572f0
19:33.12 18: 0x7f5c018776a2 - std::panicking::try::do_call::hbafbcad10c689c73
19:33.12 at libstd/rt.rs:59
19:33.12 at libstd/panicking.rs:310
19:33.12 19: 0x7f5c0188a309 - __rust_maybe_catch_panic
19:33.12 at libpanic_unwind/lib.rs:102
19:33.12 20: 0x7f5c01858f7a - std::rt::lang_start_internal::hbcd5a990678800b9
19:33.12 at libstd/panicking.rs:289
19:33.12 at libstd/panic.rs:392
19:33.12 at libstd/rt.rs:58
19:33.12 21: 0x7f5c010be214 - main
19:33.12 22: 0x7f5c001cdd1c - __libc_start_main
19:33.12 23: 0x7f5c01079028 - <unknown>
19:33.14 [style 0.0.1] cargo:rerun-if-changed=/builds/worker/c-cen-t-lnx64-ntly/build/obj-x86_64-pc-linux-gnu/dist/include/nspr/prtime.h
19:33.14 make[3]: *** [force-cargo-library-build] Error 101
19:33.14 make[2]: *** [toolkit/library/rust/target] Error 2
19:33.14 make[2]: *** Waiting for unfinished jobs....

This looks like it's probably a duplicate of bug 1520159.

You need to log in before you can comment on or make changes to this bug.