We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I see there are a few test failures 1 and 2. They appear spurious and the common factor appears to be Path::Tiny, but I can't be certain.
Path::Tiny
Locally, the following appears most likely to replicate the sysopen error in the shortest period of time.
sysopen
prove -bl -s -j4 $(find t/site -name '*.t' | sort)
The text was updated successfully, but these errors were encountered:
Okay, so that would lead me to believe that it's something not thread-safe about those tests specifically...
Maybe because I'm using Path::Tiny->tempdir? I'll change to using File::Temp and see what Travis has to say about it...
Path::Tiny->tempdir
Sorry, something went wrong.
use file::temp for tempdir instead of path::tiny
478ed89
This may fix the spurious failures on Travis... Refs #543
No branches or pull requests
I see there are a few test failures 1 and 2. They appear spurious and the common factor appears to be
Path::Tiny
, but I can't be certain.Locally, the following appears most likely to replicate the
sysopen
error in the shortest period of time.prove -bl -s -j4 $(find t/site -name '*.t' | sort)
The text was updated successfully, but these errors were encountered: