-
Notifications
You must be signed in to change notification settings - Fork 33
FIX: Use upstream/main for tools #17
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
|
@marsipu this:
With this I think we can ensure that things work. Ideally we would have a nightly scheduled job that emailed us on failure. One option is to switch to Azure Pipelines, because I know how to configure such nightly emails there. It looks like there might not be a good solution for GitHub Actions currently. But in the meantime I think this PR is a step in the right direction, so feel free to merge if you're happy! |
|
@marsipu I'm going to merge this so that the opt-in behavior can be tested properly, but feel free to comment and I'm happy to open another PR. |
|
Thanks a lot @larsoner for taking care of the test-matrix and the improved benchmarks. I really like the improved cli-interface and the presentation of the results. I am a bit confused by the results of |
upstream/mainfor now, use stableupstream/mainrather thanmarsipu/pg_test