-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Upload CI test results to S3 #23457
Upload CI test results to S3 #23457
Conversation
I've tested the xml to json conversion in a private Trino fork. That's how I came up with the length limits, since I already tried processing this with Trino. |
5302c8c
to
ceb71ab
Compare
ceb71ab
to
3945038
Compare
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.
This is great!
cb83b42
to
711ee5e
Compare
583bf11
to
cd224ab
Compare
It's ready to be merged, tested in my own fork: https://github.com/nineinchnick/trino/actions/runs/10920342447/job/30309980955 |
cd224ab
to
54d4cbe
Compare
54d4cbe
to
8f2368f
Compare
Description
Upload CI test results to S3, so we can create reports aggregating most commont failure causes in https://github.com/trinodb/reports.
This will require setting up new vars and secrets with the S3 bucket name and credentials. We can reuse the same bucket where we already copy GHA REST API data scraped in https://github.com/trinodb/reports.
Additional context and related issues
Release notes
(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text: