-
Notifications
You must be signed in to change notification settings - Fork 554
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
Run a daily test-all-versions
run
#756
Comments
I'm not against running it in every PRs, it may takes time but avoid problems after the PR is merged. To avoid too much impact we could just run tests on package that have been modified by the PR (since contribs pkgs don't depend on each other, i don't tihnk that would be an issue) |
I'll start looking at this issue if it's ok |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
That's configured in #823 |
Is your feature request related to a problem? Please describe
Some of the contrib packages have a way to run the tests against multiple versions. That's super awesome and useful! We don't run those in our CI though, namely because
Describe the solution you'd like to see
We should schedule a regular run of the full test suite with TAV for packages that have it. + maybe for release PRs.
Describe alternatives you've considered
Run it in every PR, but that could slow PR-work down too much.
The text was updated successfully, but these errors were encountered: