Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

CI: test_cover non-deterministic #1675

Closed
4 tasks
AdityaSripal opened this issue Jul 13, 2018 · 2 comments · Fixed by #1850
Closed
4 tasks

CI: test_cover non-deterministic #1675

AdityaSripal opened this issue Jul 13, 2018 · 2 comments · Fixed by #1850
Assignees
@alexanderbez
Labels
T: CI

Comments

@AdityaSripal
Copy link
Member

Summary of Bug

test_cover is nondeterministic. Running same CI test twice on same commit created two different results.

Steps to Reproduce

https://circleci.com/gh/cosmos/cosmos-sdk/16004

https://circleci.com/gh/cosmos/cosmos-sdk/16009

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@AdityaSripal
Copy link
Member Author

In above example, first detected discrepancy is in TestKeys

16004: TestKeys fails

16009: TestKeys passes

@ebuchman ebuchman self-assigned this Jul 19, 2018
@alexanderbez
Copy link
Contributor

Looked at CircleCI builds and from what I can gather its always due to an address already being in use. The example you posted did not fail at TestKeys but at a TM wal write issue which is out our scope but annoying none the less.

@alexanderbez alexanderbez mentioned this issue Jul 27, 2018
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexanderbez alexanderbez

Labels
T: CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

R4R: Fix Non-Deterministic Test Coverage cosmos/cosmos-sdk
3 participants
@ebuchman @alexanderbez @AdityaSripal