-
Notifications
You must be signed in to change notification settings - Fork 616
Add support of macrobenchmark result analysis in fireci #4323
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
Generated by 🚫 Danger |
Size Report 1Affected Products
Test Logs |
@@ -18,8 +18,10 @@ jobs: | |||
- uses: actions/[email protected] | |||
- uses: actions/setup-python@v2 | |||
with: | |||
python-version: '3.9' | |||
python-version: '3.8' |
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.
so have we been running on 3.8 for release build and 3.9 for GHA workflows?
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.
I believe so.
We didn't specify a python version in the CI dockerfile. From the cloud build log for the latest image (registry, latest build), I think it was 3.8 that has been run for release.
I tried update the docker file. Building with 3.9 works (log), but 3.10 (log) and 3.11 (log) seem not.
#4285 was reverted in #4312 as it broke the release process (#4285 requires python 3.10, release infra supports only 3.8).
This pull request adds #4285 back:
mypy
to CI checksNeeds to submit together with: