ci: get rid of failures in make-based CI#96027
Conversation
9abe3a0 to
e90b506
Compare
1. We don't post to GitHub from `make`-based CI jobs any more, and `github-post` doesn't build cleanly from `make` any more. I delete all the code related to `github-post` from `run_json_test`. 2. Delete `teamcity-check-genfiles.sh` which doesn't serve a purpose now that `vendor` is gone. Epic: none Release note: None
healthy-pod
left a comment
There was a problem hiding this comment.
Suggestion that can be done here or separately: do we need to keep running make-based Optimizer tests, make-based Random Syntax tests, and make-based Compose tests? If not we can stop scheduling the nightlies, delete teamcity-opttest.sh, teamcity-compose.sh, and teamcity-random-syntax.sh. I think teamcity-test-deadlock.sh is not used and can be deleted too but I couldn't confirm. This leaves run_json_test with only one reason to exist which is lint in teamcity-check.sh after which we can delete the whole function.
These should not be running on
AFAICT the scripts can be deleted from
I agree this script doesn't seem to be used any more. In a follow-up PR I'll look at cleaning out the |
|
bors r=healthy-pod |
|
Build failed (retrying...): |
|
Build failed (retrying...): |
|
Build succeeded: |
make-based CI jobs any more, andgithub-postdoesn't build cleanly frommakeany more. I deleteall the code related to
github-postfromrun_json_test.teamcity-check-genfiles.shwhich doesn't serve a purpose nowthat
vendoris gone.Epic: none
Release note: None