-
Notifications
You must be signed in to change notification settings - Fork 50
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
test all sources every night #315
Conversation
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.
Awesome work, @AstrakhantsevaAA
@AstrakhantsevaAA run this only on duckdb on linux. |
@AstrakhantsevaAA one more thing: we need to exclude some tests from nightly tests. We can do that using custom pytest markers: https://docs.pytest.org/en/7.1.x/example/markers.html |
@AstrakhantsevaAA maybe it makes sense to merge this even before all tests are up and running? This way we would see the stats on failing tests |
b4f9540
to
79d8164
Compare
79d8164
to
8b9633d
Compare
Tell us what you do here
verified source
)Relevant issue
issue #
More PR info
We need to check all our verified sources sometimes. We test them, but only when create or change them. They break silently all the time, and we find out about it from users or by accident.
Suggestion: we could have a nightly run, every night at 4am or so