-
Notifications
You must be signed in to change notification settings - Fork 611
build using Py3.8 and test across more OSs #506
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
Conversation
d97d7ac
to
0bca626
Compare
now this also runs on Windows 7 capa.exe 478040c |
@@ -26,10 +29,11 @@ jobs: | |||
uses: actions/checkout@v2 | |||
with: | |||
submodules: true | |||
- name: Set up Python 3.9 | |||
# using Python 3.8 to support running across multiple operating systems including Windows 7 |
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.
good comment
whats our status here? |
If we're fine with Python 3.8 I can remove the testing code and get this set up before the next release. |
bump @Ana06 and @williballenthin |
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 fixes a bug, so it should be mentioned in the changelog 😉
@@ -45,10 +46,38 @@ jobs: | |||
name: ${{ matrix.asset_name }} | |||
path: dist/${{ matrix.artifact_name }} | |||
|
|||
test_run: |
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 do not really like to test this in the build workflow. I mean, we release and if any OS fails we don't upload any binary. It would be better to test this before releasing. What about adding a test build workflow which is run in master (which should be green before releasing) and removing it from here?
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.
hm, how can we do this on a per-case basis? maybe via a specific activity type https://docs.github.com/en/actions/reference/events-that-trigger-workflows#release?
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.
What do you mean? running it only on a release PR?
My proposal was to create a build_test.yml
which is run on master:
on:
push:
branches:
- master
alternatively we could test it on every PR
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.
Instead of duplicating steps in a new workflow file my new proposal uses if
checks to test_run
on push to master or to zip
on release.
.github/workflows/build.yml
Outdated
@@ -45,10 +48,40 @@ jobs: | |||
name: ${{ matrix.asset_name }} | |||
path: dist/${{ matrix.artifact_name }} | |||
|
|||
test_run: | |||
if: github.event_name == 'push' && github.ref == 'refs/heads/master' |
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.
do this step on push to master
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 think github.event_name == 'push'
should be enough because this only runs in master
zip: | ||
if: github.event_name == 'release' |
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.
do this only for release events
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.
👍
.github/workflows/build.yml
Outdated
@@ -45,10 +48,40 @@ jobs: | |||
name: ${{ matrix.asset_name }} | |||
path: dist/${{ matrix.artifact_name }} | |||
|
|||
test_run: | |||
if: github.event_name == 'push' && github.ref == 'refs/heads/master' |
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 think github.event_name == 'push'
should be enough because this only runs in master
.github/workflows/build.yml
Outdated
@@ -75,9 +78,10 @@ jobs: | |||
run: ./${{ matrix.artifact_name }} -h | |||
|
|||
zip: |
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.
zip_and_upload
may be a better name for this (although this was not modified in this PR)
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.
updated this and the 'push' check, thanks!
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.
Looks ready to merge! 🎉 (nitpick: squashing the commit would be great 👀 )
Done! |
closes #505
also further discussion is warranted