GitHub Actions for CI on Windows #70
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Alexander-Block
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a GitHub Actions workflow for CI on a Windows VM. It installs Dyalog APL, .NET, Tatin and Cider (the latter two currently as supplied by Dyalog APL), runs all tests that can be run in batch mode, reports failures and finally publishes the code coverage report in html format as an artifact to GitHub.
The workflow is triggered by pushes to main and pull requests to main and can be triggered manually. It might be sensible to have it run in particular intervals to catch changes to Dyalog APL or .NET breaking Cider tests.
This changes in this PR outside the workflow YAML file itself are identical to #69.
Because of #64 it is expected that the test suite currently fails on windows. I mark this PR as a draft because I noted in a test run that not only (some of) the NuGet test are broken, but also the following unrelated tests that go through without problems on my local Windows machine:
Test_Misc_003
Test_Misc_015
Test_Open_001
Test_Open_008
Test_Open_050
I will try to find out why these errors occur before marking this PR as ready.