Skip to content
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

Add CI jobs for Windows #151

Merged
merged 35 commits into from
Jul 24, 2023
Merged

Add CI jobs for Windows #151

merged 35 commits into from
Jul 24, 2023

Conversation

chiphogg
Copy link
Contributor

The job builds a single-file version of the Au library, and runs a
simple test. This test is enough to reproduce the errors in #143:
https://github.com/aurora-opensource/au/actions/runs/5496101666/job/14882361539

It also catches another few compiler errors on other versions of MSVC,
which we fix here. The issue is that function parameters can't be used
in a constexpr context in general. These particular parameters are
monovalue types
(https://aurora-opensource.github.io/au/main/reference/detail/monovalue_types/),
so the compiler's being a little pedantic in enforcing this rule, but
this also means that it's easy to fix the error.

With this PR, we go from 0 to 1 in terms of CI jobs for "best effort"
platforms. This gives us a pattern we can use for future new platforms.

Helps #144.

chiphogg added 30 commits July 8, 2023 11:41
If this works, I'll need to figure out how to write a test file and
compile and run it with MSVC.

For now, I'm triggering on every push to every branch for easier
testing.
Shot in the dark --- is this why it didn't trigger?
This shouldn't make a difference, but I don't know what will.
I needed to tweak some settings on the repo.
I have no idea how to use powershell
Specifying 3.10.6 replaces 3.10.11, which makes it take way longer.
Maybe it's complaining about using a function parameter as a constant
expression?
This reverts commit 872bd5f.  We are
testing to see whether this causes the build step to fail with similar
errors.
The error didn't show up as I expected.  Maybe it will on an older MSVC.
The build is broken under the current settings.  This should fix it.
@chiphogg chiphogg added release notes: 🐛 lib (bugfix) PR fixing a defect in the library code release notes: ⚙️ repo PR affecting the way the repository works labels Jul 24, 2023
@chiphogg chiphogg requested a review from timhirsh July 24, 2023 11:47
@chiphogg chiphogg requested a review from a team as a code owner July 24, 2023 11:47
Copy link
Member

@timhirsh timhirsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

@timhirsh
Copy link
Member

Current main branch protection rules are not requiring this new job, fyi:

Screenshot 2023-07-24 at 9 28 28 AM

After landing this PR, it'd be good to add that to the list of required checks.

@chiphogg chiphogg merged commit 981ad9d into main Jul 24, 2023
@chiphogg
Copy link
Contributor Author

Since these new jobs are the first in the "best effort" tier, technically they don't have to always be passing. However, I think we want to make, well, our best effort to keep them passing, so I'll make them blocking unless and until something forces us to let them fail.

@chiphogg chiphogg deleted the add-single-file-actions#144 branch July 24, 2023 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release notes: 🐛 lib (bugfix) PR fixing a defect in the library code release notes: ⚙️ repo PR affecting the way the repository works
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants