Baunsgaard commented on PR #1628: URL: https://github.com/apache/systemds/pull/1628#issuecomment-1149648533
> As a side note, when I ran all the tests the following testcases fail, but work when executed in isolation: > > * `FederatedWorkerIntegrationCRUDTest.testWorkerAddedForMonitoring` > > * `FederatedColAggregateTest.testTernaryColSumDenseMatrix` > > * `FederatedCtableTest.federatedCtableSinglenode` (configuration [3]) > > * `FederatedFullAggregateTest.testTernarySumDenseMatrixCP` (configuration [0] and [1]) > > * `FederatedWeightedCrossEntropy` (configuration [0] and [1]) > > * `federatedWeightedCrossEntropySpark` > * `federatedWeightedCrossEntropySparkEpsilon` > * `federatedWeightedCrossEntropySparkNode` > * `federatedWeightedCrossEntropySparkNodeEpsilon` > > * `FederatedWeightedDivMatrixMultTest` all or almost all > > * `FederatedWeightedSigmoidTest` all > > * `FederatedWeightedSquaredLossTest` all > > * `FederatedWeightedUnaryMatrixMultTest` all (both configurations) > > > I remember that this is a known problem. Edit: I was behind a few commits, so this information might be outdated. Yes this is known. You can run your tests such that they repeat if failing, there you will detect these "flaky" tests. If you use IntelliJ, you can also add a new execution mode where you repeat failing tests mvn clean compile test -Dmaven.test.skip=false -Drerun.failingtests.count=1 -D automatedtestbase.outputbuffering=true -Dtest=org.apache.sysds.test.$@ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
