Thanks for the explanation, @blake.meike. I narrowed down the cause to this line of LogTest, but still can’t figure out why it’s causing these error logs. The errors are not logged when running the LogTest tests by themselves, only when running all the tests together.
This test is the only test in LogTest that actually uses testWithConfiguration(). LogTest is nearly identical to your LogTest in the Java SDK, just with the internal specific tests commented out, based on these findings.
This other test also sets the FileLogger.config, but does not cause the errors to log as the other one is doing.
Indeed that scratch directory should be writable. The only thing I can think is that it could just not exist anymore, since the scratch directories are cleaned up at the end of the test suite. The file logging should be disabled, with the config set to null at the end of the LogTests too though.