New issue
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
Getting an error in Windows during CI tests on Github that Tap won't install #61
Comments
I tested on a Wndows machine and TAP:ver<0.3.13> installed just fine so not sure what the issue is with github. |
Yeah, this has been reported to me before and no-one can reproduce it outside of github-ci. It's very mysterious, and I suspect the issue isn't really related to TAP anyway (but that's just a guess), it's just the first to trip over whatever's wrong. |
Whoa, wtf? I modified the yaml file from Logs are here: https://github.com/sdondley/Directory/actions/runs/3976471886/jobs/6816975623 |
It's a heisenbug - comes and goes - I think ugexe got closest to pinning it down to something in precompile in 2022.12. He points to the install dying here: https://github.com/rakudo/rakudo/blob/5f7ff013deb8fcab3e3599a50e2a77444dd0582b/src/core.c/CompUnit/PrecompilationRepository.pm6#L461 - but without a proper message. He thinks perhaps: https://irclogs.raku.org/raku/2023-01-04.html#01:34 |
I think "neutrinobug" is a better name for an intermittent problem - like neutrino oscillations. |
or even Schrodinger's Kittens |
OK, it looks iike simply re-running the failed job for windows separately can correct the problem on GitHub.
|
@sdondley It is not works for me... |
@atroxaper yeah, I discovered it can sometimes take several attempts. Sometimes you get lucky and it works the very first time. |
I've had a github action for zef fail 15+ times in a row; it has never passed. At some point of consistent failure the action passing is only a coincidence and we have to accept there is a legitimate bug |
I've switched from 'latest' to '2022.07' for Windows tests, and TAP install is solid / never fails. |
I downgraded to 2022.07 for all OS's:
How do I set it just for windows? UPDATE: Figured it out. At least, this seems to work as I intend:
|
https://github.com/ugexe/zef/actions/runs/4002030615/jobs/6878017528#step:9:21 is an example of zef failing its own test, including the |
I'm also seeing similar strangness when running 2022.07 on windows latest for a different module. Attempt #1 fails: https://github.com/sdondley/Distribution-Extension-Updater/actions/runs/4008470899/attempts/1 |
Is this rakudo/rakudo#5168 ? |
Is #62 related? |
I just thought of my similar problem running xtest for docs. Could it be a subtle problem with non-linear execution? UPDATEI just changed, for Windows only, a test for one of my failing Windows modules to Rakudo version '2022.07' and it's now passing! |
So the workaround is to fix the Windows version to 2022.07, right? No hint to what could be the actual error in Windows? |
Just triggered this issue on a windows github build https://github.com/pmqs/Archive-SimpleZip/actions/runs/5103285816/attempts/1
Rerunning the job made that problem go away. |
Discussion on IRC suggested this might be related to long path issues on windows; please try running the tests inside of a git clone of the repo starting from a very long working path (> 300 chars) |
I think Windows has a max path length of 256 chars Yep, just tried & it complained |
So I guess this issue is still open? But not specific to this repo? |
I'm not sure it's only that error. Honestly, I never liked TAP and can't seem to find any good reason to go back to it for any CI but one thing is sure: not all repos fail on the path issue, in fact, most of them don't. I don't know, could be that TAP itself does, it couldn't really be solved so far, from what I understand. |
Please see: https://github.com/sdondley/Directory/actions/runs/3972369620/jobs/6810208097
Error:
The text was updated successfully, but these errors were encountered: