Open dscho opened 1 week ago
This error message has been mentioned on the Cygwin mailing list in 2022, seemingly without any traction seeing as the proposed patch never made it into Cygwin, at least I cannot find it, even on their master branch.
Looking at this reply I think it became this commit in 3.3.
This error message has been mentioned on the Cygwin mailing list in 2022, seemingly without any traction seeing as the proposed patch never made it into Cygwin, at least I cannot find it, even on their master branch.
Looking at this reply I think it became this commit in 3.3.
Good find, I had overlooked that email!
But then I am really at a loss in which direction to look for a hint at a solution...
Every once in a while, a
win test
orwin+VS test
job in our CI runs fails with a very obscure "Parse errors: No plan found in TAP output" bread-crumb left behind in theprove
output. Example:Looking at those test failures shows some two dozen lines with the error mentioned in this ticket's title. Example:
This error message has been mentioned on the Cygwin mailing list in 2022, seemingly without any traction seeing as the proposed patch never made it into Cygwin, at least I cannot find it, even on their
master
branch.The same error message was mentioned again in July '24, this time on the
cygwin-developers
mailing list, again without any traction.Maybe we should integrate the proposed work-around into the MSYS2 runtime and see whether it improves things?