-
Notifications
You must be signed in to change notification settings - Fork 18
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
Adds a GitHub Action to test PyPI Releases on a Regular Schedule #29
Conversation
c7e1b58
to
a8ee013
Compare
Although the new GitHub Action is failing, the Action is actually working correctly. The following issues with pip-installed Hatchet are causing the Action to fail as expected:
Since unit tests install Hatchet via |
cb5939e
to
d05a1d6
Compare
From my perspective, there are only 3 remaining tasks for this PR:
|
003c715
to
4c3c4ec
Compare
714d0af
to
8bf1ffb
Compare
b461833
to
48d44ce
Compare
Also adds Python 3.9 to the testing matrix and removes Python 2.7
@slabasan now that we're only testing v2022.2.0 and we're not testing with Python 2.7, the runner is now passing. At this point, before merging, we should think about changing the trigger from a PR/branch push to a cron job. To that end, we need to choose how frequently we'd like this to run. Any ideas? |
@slabasan I just set a schedule for the tester. According to GitHub, the cron syntax represents the following:
|
This PR is created in response to hatchet/hatchet#443.
This PR adds a new GitHub Action that essentially performs automated regression testing on PyPI releases. It will install each considered version of Hatchet under each considered version of Python, checkout that Hatchet version's release branch, and perform the version's unit tests.
The following Hatchet versions are currently considered:
Similarly, the following versions of Python are currently considered:
Before merging, the following tasks must be done:
Replace theSuperseded by a task in a later commentworkflow_dispatch
(i.e., manual) trigger with the commented outschedule
trigger inpip_unit_tester.yaml
llnl-hatchet
instead ofhatchet
. This will be changed once thellnl-hatchet
package goes live on PyPI