We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've been seeing this intermittently in proofs CI and it should be resolved.
Running `/Users/distiller/crate/target/release/deps/storage_proofs_porep-3eae6b0d3e017065 --nocapture` running 14 tests test stacked::vanilla::challenges::test::test_calculate_fixed_challenges ... ok thread 'stacked::vanilla::cores::tests::test_cores' panicked at 'attempt to calculate the remainder with a divisor of zero', storage-proofs-porep/src/stacked/vanilla/cores.rs:149:19 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace test stacked::vanilla::cores::tests::test_cores ... FAILED thread 'stacked::vanilla::create_label::multi::tests::test_create_labels' panicked at 'poisoned lock: "PoisonError { inner: .. }"', storage-proofs-porep/src/stacked/vanilla/cores.rs:126:32 test stacked::vanilla::create_label::multi::tests::test_create_labels ... FAILED test stacked::vanilla::cache::tests::test_read_full_range ... ok [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &porep_id = [ 3, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ] [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &nodes = 1073741824 [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &expect_pathological = true test stacked::vanilla::cache::tests::test_read_partial_range ... ok test stacked::vanilla::graph::tests::test_high_parent_bits ... ok [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &porep_id = [ 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ] [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &nodes = 2147483648 [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &expect_pathological = true test stacked::vanilla::graph::tests::test_shuffle ... ok [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &porep_id = [ 8, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ] [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &nodes = 1073741824 [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &expect_pathological = false [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &porep_id = [ 9, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, ] [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &nodes = 2147483648 [storage-proofs-porep/src/stacked/vanilla/graph.rs:552] &expect_pathological = false test stacked::vanilla::graph::tests::test_graph_distribution_pathology ... ok test stacked::circuit::hash::tests::test_hash2_circuit ... ok test stacked::vanilla::challenges::test::challenge_partition_equivalence ... ok test stacked::vanilla::graph::tests::test_exp_parent_histogram ... ok test stacked::circuit::hash::tests::test_hash_single_column_circuit ... ok test stacked::vanilla::challenges::test::challenge_derivation ... ok test stacked::circuit::create_label::tests::test_create_label ... ok failures: failures: stacked::vanilla::cores::tests::test_cores stacked::vanilla::create_label::multi::tests::test_create_labels test result: FAILED. 12 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 5.70s error: test failed, to rerun pass '-p storage-proofs-porep --lib' Exited with code exit status 101 CircleCI received exit code 101
CI tests always pass.
This may be a real bug, but most likely just related to the CI darwin resources.
The provided log.
The text was updated successfully, but these errors were encountered:
Resolved with #1454
Sorry, something went wrong.
No branches or pull requests
Description
I've been seeing this intermittently in proofs CI and it should be resolved.
Acceptance criteria
CI tests always pass.
Risks + pitfalls
This may be a real bug, but most likely just related to the CI darwin resources.
Where to begin
The provided log.
The text was updated successfully, but these errors were encountered: