-
Notifications
You must be signed in to change notification settings - Fork 110
fix intermittent failures in incentives simulation tests #1899
Comments
tagging @janos and @holisticode (feel free to edit the issue if you have additional relevant info or corrections) |
@mortelli does this actually flake on travis or only when running locally with high test count? if it is the case of the latter, then it is unfortunate but i'd say not very critical. we have other tests with the same symptoms. does it also occur when you run it multiple times enclosed by a |
@acud Failures are more frequently occurring on Ubuntu 19.10 running as a guest host in VirtualBox. This is how I was able to reproduce them for debugging. The only symptom that I managed to find is that there are stored balances with double amount of payout threshold only stored when the error happens. But I did not manage to fix the problem with that information. |
both. i was actually made aware of this error through the AppVeyor failed builds, and then managed to reproduce it locally with a high test count. it blocked multiple PRs and this is why i looked into it in the first place.
it does not. |
it looks like pending cheques introduced a new flaky error in the TestMultiChequeSimulation test. I can only reproduce it inside a vm so far:
|
Probably unrelated but I noticed that the tests recognise received cheques by the |
The |
Here is some log output. (Don't worry about the
|
there is an occasional, hard-to-reproduce bug occurring in
swap/simulations_tests.go
.it looks like this:
it's currently unknown whether this is a proper bug, or something wrong with the sim tests themselves. things are pointing towards the former.
tests known to be affected by this bug:
TestPingPongChequeSimulation
TestMultiChequeSimulation
high
count
values when runningswap
tests can sometimes trigger the bug, e.g.:hence the bug is suspected to have something to do with concurrency/synchronization.
the
incentives-simulations-bug
branch is available for repeating CI tests under PR #1893.The text was updated successfully, but these errors were encountered: