New "test info" file requires that the current directory be writable

[bleargh45]

The recently added "test info" file (see

Test2-Harness/lib/App/Yath/Command/test.pm

Line 263 in 32e0ca1

my $info_file = "./.test_info.$$.json";

), used for yath resources, requires that Yath be run from a directory which is writable. When running builds/tests inside of a Docker Container, though, this may not always be the case.

Should this file not be recorded into a temp directory (such as /tmp) instead?

[exodist]

Ah, I do understand the problem.

The nature of this file, and its purpose do make it potentially useless outside of the home dir. Though I may be able to work out something like I did for the persistent runner's file, which no longer depends on the home dir.

As for this (and the persistent runners) when the repo dir is not writable, I think I can make an option to disable it, and make that option's value depend on the writability of the repo dir.

I will work on this next time I have a moment, which unfortunately may mean it has to wait for the week of thanksgiving.

[bleargh45]

For the moment, I have been able to disable the use of the file by setting TEST2_HARNESS_NO_WRITE_TEST_INFO=1 in my ENV, but that obviously does mean that the yath resources command does not work (which for the moment is not an issue for me).

[abraxxa]

I was just hit by this issue too because the file breaks the test run by Dist::Zilla::Plugin::Test::DistManifest.
The env var TEST2_HARNESS_NO_WRITE_TEST_INFO seems to be undocumented at the moment.