-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create CI #2
Conversation
.github/workflows/ci.yml
Outdated
run: | | ||
xcrun swift test -c release --enable-code-coverage -Xswiftc -enable-testing |
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.
I don't have permissions to set up Codecov in this repo so I didn't set that up. We’ll Get There™
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.
- name: Checkout Repo | ||
uses: actions/checkout@v4 | ||
- name: Build and Test Framework | ||
run: swift test -c release --enable-code-coverage -Xswiftc -enable-testing |
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.
this is becoming a habit of mine in open source libs: test in release!
makes things a bit slower in CI but I have caught a few esoteric issues this way.
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.
though testing in release on macOS yields an error executing the CLI, which... I don't get why. works on linux at least.
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.
Oh interesting! I've never thought about testing in release. Let's try it out!
No description provided.