You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: fail fast may cause Serial spec or cleanup Node interrupted (#1178)
* fix: fail fast may cause Serial spec or cleanup Node interrupted
* tighten up edges around abort behavior
1. inter-process aborts should not interrupt cleanup nodes
2. whenever we fetch interrupt status, check and see if an abort has happened. if it has ensure we return the latest, correct, abort state. this allows us to avoid accidentally starting the next spec because the ABORT_POLLING_INTERVAL hasn't fired yet
* fix race condition in internal integration suite
* fix internal test race condition
---------
Co-authored-by: Onsi Fakhouri <onsijoe@gmail.com>
You should call SetUpForParallel() first, then call RunFixtureInParallel()
104
+
105
+
this is, at best, an approximation. There are some dsl objects that can be called within a running node (e.g. DeferCleanup) that will not work with RunFixtureInParallel as they will attach to the actual internal_integration suite as opposed to the simulated fixture
106
+
107
+
moreover the FakeInterruptHandler is not used - instead a real interrupt handler is created and configured with the client generated by SetUpForParallel. this is to facilitate the testing of cross-process aborts, which was the primary motivator for this method.
108
+
109
+
also a noopProgressSignalRegistrar is used to avoid an annoying data race
0 commit comments