Run unit tests on a schedule#3119
Open
brianaydemir wants to merge 7 commits intoPelicanPlatform:mainfrom
Open
Conversation
brianaydemir
added
test
Contributor
Author
|
I'm open to a better (or different) name for the workflow. At the moment, I've chosen to follow the naming scheme used by the other testing workflows. |
Contributor
Author
|
To test this PR: I switched the default branch for my fork to the branch this PR is based on, and then I manually triggered the workflow 13 times. |
turetske
reviewed
Feb 26, 2026
Collaborator
There was a problem hiding this comment.
@brianaydemir Why only linux? Why not MacOS as well? I say this because I know we have had flaky tests that were also platform specific.
I actually had written everything up to and including the `run-tests` job when I asked Copilot to work on `analyze-tests`.
- Add `workflow_call` trigger to `test-macos.yml` and `test-windows.yml` so they can be used as reusable workflows. - Add `test-macos-scheduled.yml` and `test-windows-scheduled.yml`, which mirror `test-linux-scheduled.yml`: each runs the corresponding test workflow on a daily schedule and then analyzes JUnit artifacts across the 14 most recent runs to surface flakey tests. - Extract the inline Python from `test-linux-scheduled.yml` into `.github/scripts/analyze_junit_results.py`. The script is generalized to strip `-Linux`, `-macOS`, and `-Windows` suffixes from matrix variant names, so all three scheduled workflows can share it. - Extract the identical inline shell from the "Download artifacts" step in all three scheduled workflows into `.github/scripts/download_junit_artifacts.sh`. The script takes the workflow name as $1 and relies on standard GitHub Actions environment variables (`GITHUB_REPOSITORY`, `GITHUB_RUN_ID`, `GITHUB_STEP_SUMMARY`). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
brianaydemir
force-pushed
the
find-flakey-tests
branch
from
76395d5 to
3b57a2c
Compare
- bandit B405/B314: Add `# nosec` with justification comment (XML is
from our own CI runner, not user input).
- pylint W0718: Narrow broad `Exception` catch to
`(ET.ParseError, OSError)`.
- mypy var-annotated: Add explicit type annotation for
`failures_by_matrix`.
- mypy union-attr: Guard against `testcase.get('classname')` returning
`None` by using `or ""`.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This new GitHub Actions workflow intends to operate as follows:
The idea is to make it easier to identify "flakey" unit tests vs. those that are reliably failing. The notification mechanism, or lack thereof, is perhaps not ideal, but at we can start accumulating data.