Automatic compilation checking via github actions#64
Conversation
MarcCote
left a comment
There was a problem hiding this comment.
We could avoid compiling the jar on all individual runs by making the test runs depend on a parent run that compiles the jar. That parent run could run on Linux.
.github/workflows/tests.yaml
Outdated
| - uses: olafurpg/setup-scala@v10 | ||
| - name: Check scienceworld compilation | ||
| run: ./simulator/package.sh |
There was a problem hiding this comment.
Ideally, we want to use that compiled jar file to run the tests as well.
There was a problem hiding this comment.
Artifact can be share between runs https://docs.github.com/en/actions/using-workflows/storing-workflow-data-as-artifacts
…uns depend on it.
|
@AndKaminer I made PR to your branch with the changes I have in mind. This is how it looks like when it is running |
Thanks for doing that. Sorry for taking out a PR and ghosting. I had some unexpected things come up. I'll take a look. |
Use a separate Github Action to build the JAR.
Looks great! I just merged on my branch, so it should be good to merge here. |
No worries. Thanks for initiating all the changes. |
|
Fixes #60 |
Use this github action to setup scala. Then run package.sh. If it fails, the test fails and vice versa. The only problem with this is that it behaves oddly on Windows. The action can only pass on windows. It never fails, even when it fails on unix-based systems.
This ^ is the output of the test on Windows.
Whereas this ^ is the output on unix systems.
It appears to me that the script isn't even running on windows. Unfortunately, I don't have a windows machine, so I can't directly test on windows.
Regardless, if something goes wrong with the compilation, tests do still fail. You just only see it in macos or ubuntu.