The unit test DumpManagerTest.testWriteError() failed on CI platform

This unit test failed in CI. The aim of this test is for test coverage of the exception thrown by DumpManager.activate(final File file).

changed milestone to %2.2

added Bug label

On developers computer, the

DUMP.set(new Dump(new PrintWriter(file, "UTF-8")))

throws a FileNotFoundExecption, but no exception is thrown on the CI.

In the unit test:

dump.setReadOnly();

gives true on developper computer and CI platform.

A @Ignore was added to this unit test until a solution if found

We should probably try to add a call to variousRuggedCalls() between DumpManager.activate(dump) and Assert.fail("an exception should have been thrown"). This way, we really try to write, we don't only open the file.

mentioned in commit eddea631

I try it but it did not solve the problem : see job #932

The run is Ok on developper computer but not on CI : same problem

Failed tests: testWriteError(org.orekit.rugged.errors.DumpManagerTest): an exception should have been thrown

The problem seems linked to the fact the CI runs the tests under root account, which can bypass restricted files permissions. Running the test on a developer machine under root gave me the same failure.

We have now to find if either we can get CI run tests with a less privileged account or if we can set up a different strategy to ensure a write error is triggered and detected.

mentioned in commit efb03d74

closed

added Resolved label