Sometimes xvfb-run doesn't relinquish the display port in time, which leads to xvfb-run: error: Xvfb failed to start errors. This is fixed in 3dc7aa3 by only starting a single framebuffer for all tests.
The tests are SIGABRTed on 6.7BC, 7.{7,8,9}CS. I think this is a genuine issue with those versions of Racket, because, across many runs (1, 2, 3), it's always those versions that fail. The fix here is to allow failures on those versions.
I finally had a bit of time to look into bogdanp/setup-racket#29.
It looks like there were two issues here:
1) Sometimes `xvfb-run` doesn't relinquish the display port in time, which leads to `xvfb-run: error: Xvfb failed to start` errors. This is fixed in 3dc7aa3 by only starting a single framebuffer for all tests.
2) The tests are `SIGABRT`ed on 6.7BC, 7.{7,8,9}CS. I think this is a genuine issue with those versions of Racket, because, across many runs ([1](https://github.com/Bogdanp/beautiful-racket/actions/runs/823468578), [2](https://github.com/Bogdanp/beautiful-racket/actions/runs/823483250), [3](https://github.com/Bogdanp/beautiful-racket/actions/runs/823494290)), it's always those versions that fail. The fix here is to allow failures on those versions.
I finally had a bit of time to look into bogdanp/setup-racket#29.
It looks like there were two issues here:
Sometimes
xvfb-rundoesn't relinquish the display port in time, which leads toxvfb-run: error: Xvfb failed to starterrors. This is fixed in3dc7aa3by only starting a single framebuffer for all tests.The tests are
SIGABRTed on 6.7BC, 7.{7,8,9}CS. I think this is a genuine issue with those versions of Racket, because, across many runs (1, 2, 3), it's always those versions that fail. The fix here is to allow failures on those versions.Thanks for the insight!
216536ef29.Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.