-
Notifications
You must be signed in to change notification settings - Fork 77
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
Make use of GitHub CI #107
Conversation
…lt (master) branch.
…1-11/github-ci because these warnings cause GitHub CI to fail <https://github.com/Ravenbrook/mps/actions/runs/3892932541/jobs/6644932572#step:4:215>.
…the shim we made for Travis CI.
… script is secretly a batch file and needs to use "call".
…ci to explore hybrid scheme between GitHub CI and Travis CI.
…cting the permissions required on the token.
…persuade configure script to use Clang.
…xclude XC*GC correctly.
… and is now inconsistent with them. Cross-referenced, added FIXME notes to update documentation.
Reverted to draft while I update and cross-reference design.mps.tests.ci. |
…tHub CI and Travis CI and tag them.
…f the document on GitHub.
…eferences to design, references, etc.
…nce on code we bring in to the project.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…ate irrelevant differences from branch/2023-01-06/gcc-11.3.0-warnings from code review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Executing pull request merge procedure. Checklist results
|
(cherry picked from commit 3c62e29)
Implementing use of GitHub CI in parallel with Travis CI to help with #109 .
Maintaining both helps with #98 (comment)
I suggest reviewing and merging #104 to master before this, because it's included.