This will avoid having the dangling proof cleanup task triggered after the fixture processor is destructed. This only affects the processor unit tests.
Details
Details
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Branch
- avalanche_stop_scheduler_tests
- Lint
Lint Passed - Unit
No Test Coverage - Build Status
Buildable 20007 Build 39703: Build Diff lint-circular-dependencies · build-without-wallet · build-diff · build-debug · build-clang-tidy · build-clang Build 39702: arc lint + arc unit
Event Timeline
Comment Actions
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.
Comment Actions
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.
Comment Actions
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.
Comment Actions
The build failed due to an unexpected infrastructure outage. The administrators have been notified to investigate. Sorry for the inconvenience.
Comment Actions
This only fixes the case where the scheduled cleanup happens post-test-cleanup, but not the case where m_processor is replaced and the test is still running, therefore the first processor instance's cleanup gets run on the destructed processor. I think my solution here is more complete: D11965