…plicate names of tests within the same suite
… tests, the run method on the test suite needs to run instead of flattening and running individual tests
…f we have the remaining slowliness simply isolated to specific tests
… will only be loaded by that dedicated process which will run them and then proceed toa regular queued test runs
…test suites for test suites with non-atomic test cases; created an env variable NONATOMIC_TEST_SUITES; test suites will run first guranteing the process untilization and then atomic test cases will kick in
…for queue test cases is an empty string
…a CI exception is not known. For now, rescue and output the error so that the ruby process stays alive
…e tracking - when CI reporter switches between test suites, it forces the suite to finish too early, this can be fixed by guaranteeing the order of the cached test cases, instead of using the unordered hash for lookups (in QueuedTestSuite).
…o no file overwrite or other concurrency errors happen; however tests still do not add up yet
…EDUCED_TEST_SUITE_SAMPLE to control the behaviour of parallelization; also using these parameters able to isolate the problem when CI reports are being overwritten if test cases within the same file are being executed in parallel - this also causes intermittent CI runtime exception which brings down ruby instances and may be a reason for performance problems
…e debugging to see why so slow - maybe Drb?
…ing on each process
…to ensure that whatever process enters first will be able to close the queue, also queueing test suites and falttening only when running - not optimized yet