Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Fix test: corpus_inaccessible (panic) #10019

Merged
merged 1 commit into from
Dec 5, 2018

Conversation

mattrutherford
Copy link
Contributor

@mattrutherford mattrutherford commented Dec 5, 2018

If system uptime is less than the duration in the test, thread will panic:

thread 'cache::tests::corpus_inaccessible' panicked at 'overflow when subtracting duration from instant'

Reduced duration to 20 seconds (from 5 hours) to make it unlikely the test will fail due to this condition.

Since no operations on Instant in this module carry a similar risk (outside of the tests), it doesn't seem warranted to depend on an external crate to fix the test.

Closes: 9957

If system uptime is less than the duration in the test, thread
will panic due to: 'overflow when subtracting duration from instant'.

Changed duration to 20 seconds to make it unlikely the test will
fail due to this condition.

Since no operations that carry a similar risk of panic occur outside
of the tests, it doesn't seem warranted to depend on an external crate
to fix this.
@parity-cla-bot
Copy link

It looks like @mattrutherford signed our Contributor License Agreement. 👍

Many thanks,

Parity Technologies CLA Bot

@mattrutherford mattrutherford added A0-pleasereview 🤓 Pull request needs code review. M4-core ⛓ Core client code / Rust. labels Dec 5, 2018
@5chdn 5chdn added this to the 2.3 milestone Dec 5, 2018
@ordian ordian added A8-looksgood 🦄 Pull request is reviewed well. and removed A0-pleasereview 🤓 Pull request needs code review. labels Dec 5, 2018
@mattrutherford mattrutherford merged commit 2e0246a into master Dec 5, 2018
@mattrutherford mattrutherford deleted the mr-9957-corpus-inaccessible-test branch December 5, 2018 15:39
@Tbaut Tbaut mentioned this pull request Dec 11, 2018
6 tasks
niklasad1 pushed a commit that referenced this pull request Dec 12, 2018
If system uptime is less than the duration in the test, thread
will panic due to: 'overflow when subtracting duration from instant'.

Changed duration to 20 seconds to make it unlikely the test will
fail due to this condition.

Since no operations that carry a similar risk of panic occur outside
of the tests, it doesn't seem warranted to depend on an external crate
to fix this.
Tbaut added a commit that referenced this pull request Dec 13, 2018
* bump beta to 2.2.5

* Fix empty steps (#9939)

* Don't send empty step twice or empty step then block.

* Perform basic validation of locally sealed blocks.

* Don't include empty step twice.

* Strict empty steps validation (#10041)

* Add two failings tests for strict empty steps.

* Implement strict validation of empty steps.

* ethcore: enable constantinople on ethereum (#10031)

* ethcore: change blockreward to 2e18 for foundation after constantinople

* ethcore: delay diff bomb by 2e6 blocks for foundation after constantinople

* ethcore: enable eip-{145,1014,1052,1283} for foundation after constantinople

* Change test miner max memory to malloc reports. (#10024)

* Fix: test corpus_inaccessible panic (#10019)

If system uptime is less than the duration in the test, thread
will panic due to: 'overflow when subtracting duration from instant'.

Changed duration to 20 seconds to make it unlikely the test will
fail due to this condition.

Since no operations that carry a similar risk of panic occur outside
of the tests, it doesn't seem warranted to depend on an external crate
to fix this.

* Bump crossbeam. (#10048)
niklasad1 pushed a commit that referenced this pull request Dec 16, 2018
If system uptime is less than the duration in the test, thread
will panic due to: 'overflow when subtracting duration from instant'.

Changed duration to 20 seconds to make it unlikely the test will
fail due to this condition.

Since no operations that carry a similar risk of panic occur outside
of the tests, it doesn't seem warranted to depend on an external crate
to fix this.
insipx pushed a commit to insipx/parity-ethereum that referenced this pull request Dec 17, 2018
If system uptime is less than the duration in the test, thread
will panic due to: 'overflow when subtracting duration from instant'.

Changed duration to 20 seconds to make it unlikely the test will
fail due to this condition.

Since no operations that carry a similar risk of panic occur outside
of the tests, it doesn't seem warranted to depend on an external crate
to fix this.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A8-looksgood 🦄 Pull request is reviewed well. M4-core ⛓ Core client code / Rust.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

corpus_inaccessible test is unreliable
5 participants