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
gha: Run integration tests in GHA #22900
Conversation
fba6c07
to
068a4cd
Compare
51506ee
to
607dee2
Compare
922fe06
to
38e17d8
Compare
Full CI is not required, changes are related to travis and GHA only. |
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 guess we don't care about having too many GHA running anymore?
I think so, it's a perk of being CNCF project if I am not wrong. |
38e17d8
to
caf2ef5
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.
I'd have to take another look at the GHA when I'm fresher, but I noticed a couple of things while glancing through.
I wonder about the output, is it reasonable to have 16K lines of output in the workflow run? I wonder if we could sprinkle some make --quiet
and/or V=0
make magic to quieten things down. On Travis we seem to get around 800 lines, so something must be subtly different about the environment variables or something, such that we don't flood the logs wit hso much output. In this case, the GitHub interface visibly lags when you go to inspect the results.
This failed at the end of the test too, should we install goveralls?
./.travis/build.sh: line 10: /home/runner/gopath/bin/goveralls: No such file or directory
caf2ef5
to
28a5f1c
Compare
I think this step failed in travis as well, so I just remove it in script.
|
A lot of failures in GHA are due to SBOM failure in image jobs, the new IntegrationTest is successfully ran in https://github.com/cilium/cilium/actions/runs/3966354144/jobs/6797060899 |
28a5f1c
to
d46e9a9
Compare
Given
Was this addressed? If yes, I guess this is ready to merge, no? |
Yes, this point is addressed, the recent run contains only 500+ log lines. |
Current travis CI is used to run integration-tests target only, however, this can be achieved with github action easily (at least for amd64). Signed-off-by: Tam Mach <tam.mach@cilium.io>
d46e9a9
to
8c92c73
Compare
The changes here are only to add new IntegrationTest GHA, full CI is not required. As recent run is good and all required reviews are in, I am marking this ready to merge. https://github.com/cilium/cilium/actions/runs/4071443474/jobs/7013252483 |
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.
❤️❤️❤️
@gandro oh yes they were! Sorry. |
Description
Current travis CI is used to run integration-tests target only, however, this can be achieved with GitHub action easily (at least for amd64).
Signed-off-by: Tam Mach tam.mach@cilium.io
Testing
Both jobs are taking around 20 mins to complete, GHA job is having a shorter bootstrap time compared to Travis, hence from UX point of view, GHA provides a faster feedback, not to mention that Cilium contributors are already familiar with GHA ops such as re-run, checking logs, etc.
Note
Not sure if arm64 run in travis provides any added value, if not, we can just remove travis completely and refactor the scripts a little bit.