Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
2857: Fix leaks of ≈21 more wallets in integration tests r=rvl a=Anviking - [x] Replace 3 manual calls to `Link.postWallets` with the `ResourceT` `postByronWallet` - [x] Also make `createWalletFromPublicKeyViaCLI` run in `ResourceT` ### Comments - 21 wallets is a pretty significant number, so will be good to fix. Although the leaks were at the end of the tests, which lessens the impact. - There seem to be _some_ concurrency related leaks. #### Before second fix - --match "WALLET" -j 1 ->18 leaks, all at the end #### After fixes - --match "WALLET" -j 1, no leaks - --match "WALLET" -j 8, 10 leaks (3 BUSY, 6 others) ``` SQLITE_BUSY in logs: ica.14828b804a1ebe804caddd1abb5d314d2be0a62a.sqlite ica.25341683360a040721f587d069b95762b302f608.sqlite rnd.5fc0960622bc4d3a5d366a0920dfd9b5ef578ced.sqlite rnd.81273c47add77e98b3993e01cab8b2a836cd48b7.sqlite she.95cff5e68f07b759c72d4da4f1aa96e0b101bba2.sqlite she.a99218ce4bbc77f05617d642c0595246621b67b6.sqlite Remaining DBs: ica.14828b804a1ebe804caddd1abb5d314d2be0a62a.sqlite ica.25341683360a040721f587d069b95762b302f608.sqlite rnd.5fc0960622bc4d3a5d366a0920dfd9b5ef578ced.sqlite ica.ed49f6e7723fa2c15575c147566981beab6aba3e.sqlite rnd.693940686b48985ab6ec8035a56575e0473e96de.sqlite rnd.81273c47add77e98b3993e01cab8b2a836cd48b7.sqlite sha.9316fc445533f9e58becf0d367d3a9404585ea86.sqlite she.3464b427c15341dab8aaf6d89c8f79e5f24f9eae.sqlite she.a0bd7c6accac92d54fb667bf32bcba4db4cd552f.sqlite stake-pools.sqlite ``` <!-- Additional comments, links, or screenshots to attach, if any. --> ### Issue Number ADP-1090 2858: Add (Instance of #ISSUE) re-write rule for bors comments r=rvl a=Anviking - [x] Add simple re-write rules for bors-failure tags using annotations in Github issue titles ### Comments This gives us a fairly easy way to close specific tickets in favor of a more general one, without having to edit the corresponding bors-comments. This is done by writing e.g. "(Instance of #2)" for issue #1, if you want re-annotate failures from #1 as really being from #2. **Example:** #2855 <!-- Additional comments, links, or screenshots to attach, if any. --> ### Issue Number <!-- Reference the Jira/GitHub issue that this PR relates to, and which requirements it tackles. Note: Jira issues of the form ADP- will be auto-linked. --> Co-authored-by: Johannes Lund <johannes.lund@iohk.io>
- Loading branch information