Skip to content
This repository has been archived by the owner on Jan 22, 2025. It is now read-only.

Unreliable test failure observed on CI: test_boot_validator_from_file #1513

Closed
jackcmay opened this issue Oct 16, 2018 · 1 comment
Closed

Comments

@jackcmay
Copy link
Contributor

---- test_boot_validator_from_file stdout ----

  | thread 'test_boot_validator_from_file' panicked at 'assertion failed: (left == right)
  | left: 500,
  | right: 1000', tests/multinode.rs:465:5
  | note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.
  | stack backtrace:
  | 0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
  | at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
  | 1: std::sys_common::backtrace::print
  | at libstd/sys_common/backtrace.rs:71
  | at libstd/sys_common/backtrace.rs:59
  | 2: std::panicking::default_hook::{{closure}}
  | at libstd/panicking.rs:211
  | 3: std::panicking::default_hook
  | at libstd/panicking.rs:221
  | 4: std::panicking::rust_panic_with_hook
  | at libstd/panicking.rs:475
  | 5: std::panicking::continue_panic_fmt
  | at libstd/panicking.rs:390
  | 6: std::panicking::begin_panic_fmt
  | at libstd/panicking.rs:345
  | 7: multinode::test_boot_validator_from_file
  | at tests/multinode.rs:465
  | 8: multinode::__test::TESTS::{{closure}}
  | at tests/multinode.rs:441
  | 9: core::ops::function::FnOnce::call_once
  | at /checkout/src/libcore/ops/function.rs:223
  | 10: <F as alloc::boxed::FnBox>::call_box
  | at libtest/lib.rs:1451
  | at /checkout/src/libcore/ops/function.rs:223
  | at /checkout/src/liballoc/boxed.rs:642
  | 11: __rust_maybe_catch_panic
  | at libpanic_unwind/lib.rs:105
  |  

@mvines
Copy link
Contributor

mvines commented Oct 18, 2018

Dup of #1484

vkomenda pushed a commit to vkomenda/solana that referenced this issue Aug 29, 2021
* lending: Update JS tests to solana-test-validator

* Add solana tools install

* Fix oopsie on the path

* Move where deployed programs go
brooksprumo pushed a commit to brooksprumo/solana that referenced this issue May 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants