Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
2696: Timeout earlier on SQLITE_BUSY when deleting wallets in tests r=rvl a=Anviking # Issue Number ADP-827 # Overview - [x] Set `CARDANO_WALLET_INTEGRATION` env var in integration tests - [x] Change timeout to close all connections from `60s` to `2s` if `CARDANO_WALLET_INTEGRATION` is set. # Comments - Workaround that should make CI faster (and perhaps a bit more stable), until we have time to investigate and address the underlying issue and its effects in production. The problem in production is likely much less serious, as users likely don't create and delete wallets as often as in our integration tests. - Locally, running `stack test cardano-wallet:integration --ta '-j 6'` I get: - 2s -> 335s - 5s -> 380s - 60s (without the `setEnv`) -> 1190s So that's why I went with 2s rather than 5s. <!-- Additional comments or screenshots to attach if any --> <!-- Don't forget to: ✓ Self-review your changes to make sure nothing unexpected slipped through ✓ Assign yourself to the PR ✓ Assign one or several reviewer(s) ✓ Jira will detect and link to this PR once created, but you can also link this PR in the description of the corresponding ticket ✓ Acknowledge any changes required to the Wiki ✓ Finally, in the PR description delete any empty sections and all text commented in <!--, so that this text does not appear in merge commit messages. --> 2698: Make test cluster epoch length twice as long r=Anviking a=Anviking # Issue Number <!-- Put here a reference to the issue that this PR relates to and which requirements it tackles. Jira issues of the form ADP- will be auto-linked. --> ADP-979 # Overview <!-- Detail in a few bullet points the work accomplished in this PR --> - [x] Make epoch length twice as long to help epoch-sensitive tests (see commit message) # Comments <!-- Additional comments or screenshots to attach if any --> <!-- Don't forget to: ✓ Self-review your changes to make sure nothing unexpected slipped through ✓ Assign yourself to the PR ✓ Assign one or several reviewer(s) ✓ Jira will detect and link to this PR once created, but you can also link this PR in the description of the corresponding ticket ✓ Acknowledge any changes required to the Wiki ✓ Finally, in the PR description delete any empty sections and all text commented in <!--, so that this text does not appear in merge commit messages. --> Co-authored-by: Johannes Lund <[email protected]> Co-authored-by: Rodney Lorrimar <[email protected]>
- Loading branch information