S32-io/IO-Socket-INET-UNIX.t is busted #718
Comments
|
Was that the only one failing, or were there more like this? |
|
Thanks for replying quickly! This is the only one failing persistently and confusingly, I think, others are fine. There are also https://github.com/Raku/roast/blob/master/S17-procasync/kill.t and https://github.com/Raku/roast/blob/master/MISC/bug-coverage-stress-6.d.t that fail consistently under heavy load (they are flappers, really) which I would like to do something with, but I remember last time it was discussed people talking about impossibility to really fix it anyhow. |
Kaiepi
pushed a commit
to Kaiepi/roast
that referenced
this issue
Apr 4, 2021
|
Sorry for the late response. This is a huge oversight on my part, and should be a relative path of some sort; |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The test creates a relative file in the directory to work with and this has costed us some hours (and money for me) lost to release, which is LTA.
The failure looks this way:
># Socket path '/home/koto/Devel/perl6-dev/R/rakudo/tools/releasable/temp/rakudo-test/rakudo-2021.02/t/spec/S32-io/test.sock' is too long (max length supported by this platform is 107 characters)Why not open a file in $*TMP instead to prevent ^?
The text was updated successfully, but these errors were encountered: