-
Notifications
You must be signed in to change notification settings - Fork 42
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
Fix scons tests #448
Fix scons tests #448
Conversation
Feels like it's potentially a bug that the tests need an X server, but I guess it doesn't really matter that much – it's more important that the tests run at all.
Have you checked to make sure that the current working directory that scons uses to run the tests is the directory that contains the dlls? If you've already covered that avenue, then sure, we can open an issue and defer it for now. |
Co-authored-by: Celtic Minstrel <[email protected]>
Yeah... I've tried so many things. When I get a chance, I'll write them up in #449. |
This looks to be working. The last two commits could be squashed together but I'm leaving them for now to show why the double-quote syntax doesn't match the rest of ci.yml. |
Ready for this to merge if you are, @CelticMinstrel |
I've been trying to pave the way for #441 by making the scons ci builds fail when the tests fail.
This proved troublesome because the Linux and Win-Scons builds have been failing the tests silently for quite a while.
For some reason, Linux needs an X server to run the tests -- this was a pretty trivial fix because a utility is included on Ubuntu github actions runners called
xvfb
which I had never heard of but seems really awesome. It runs a headless X server for CI workflows. Using this fixed that problem.(Note for the future: there's a github action that lets you use
xvfb
on Windows and Mac. Maybe we could someday even be running our full replay test suite on CI for all three platforms this way. I don't know how sophisticated it is.)Now, for win-scons the tests are failing with an error code which I think indicates missing DLLs. I've tried so many different things to fix it, but I can't repro this failure on my own machine. On my PC, the tests run and succeed through Scons. I'm at my wits' end and I'm starting to think it's a poor use of time to keep making this a blocking issue. So I would suggest that we should make the win-scons workflow succeed if it compiles correctly, but issue a warning that the tests didn't run. @CelticMinstrel would this be okay with you, alongside opening a github issue for the real problem?
I'm also trying to trim down the other Github actions warnings, so that the win-scons warning (which I haven't implemented yet) will stand out.