[SERVER-65830] BGHook does not stop before aborting the fixture due to a test failure Created: 20/Apr/22  Updated: 27/Oct/23  Resolved: 22/Apr/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Works as Designed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Server Tooling & Methods
Operating System: ALL
Participants:
Linked BF Score: 148

 Description   

This was observed in a build failure. The replica set fixture was being stopped due to a test failure.

[j1] Stopping all members of the replica set...
[fsm_workload_test:job1_fixture_abort_0] Aborting the fixture ReplicaSetFixture (Job #1) due to test failure.

However, the SimulateCrash background hook was still running during the teardown, causing it to fail.

[SimulateCrash:job1] | 2022-04-08T04:30:08.117Z F  CONTROL  20574   [-] "Error during global initialization","attr":{"error":{"code":38,"codeName":"FileNotOpen","errmsg":"Can't initialize rotatable log file :: caused by :: Failed to open /data/db/job1/resmoke/node2/simulateCrashes/validate.log"}}



 Comments   
Comment by Robert Guo (Inactive) [ 22/Apr/22 ]

The hooks and fixtures are designed to be independent. Could the hook be designed to check the state of the fixture before running? Closing as works as designed for now but please feel free to reopen if needed.

Generated at Thu Feb 08 06:03:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.