We've had intermittent trouble with some of the basic tests on lower-performance or lower number of CPU machines we use in our CI system for testing.
The same tests never fail on higher-performance/higher number of CPU machines. We believe this may be due to a race in the test definition and a slightly different order of execution resulting from a lower number of CPUs. The addition a short wait before the test is confirmed failed will resolve - which is a valid change as there are no specific timing requirements in FDC3 for the things being tested.
We've had intermittent trouble with some of the basic tests on lower-performance or lower number of CPU machines we use in our CI system for testing.
The same tests never fail on higher-performance/higher number of CPU machines. We believe this may be due to a race in the test definition and a slightly different order of execution resulting from a lower number of CPUs. The addition a short wait before the test is confirmed failed will resolve - which is a valid change as there are no specific timing requirements in FDC3 for the things being tested.