Closed lwhsu closed 3 years ago
Do you realize that every task spins up a new VM? This would run faster if you condense everything into one task (with the two-release matrix) and used multiple scripts instead.
Yes, my first approach was trying to align with what we did with travis-ci. I was also thinking of integrating everything into one task, but that has one drawback: we cannot easily tell the failure is in build or just api-doc, and it would get worse if we add gcc build later. BTW, the tasks are executed in parallel, perhaps not slower than executing the checks sequentially. It does consumes more VM resources, though.
@googlebot rescan
(Mass-triggering a rescan of all open PRs as I have just configured automated CLA checks but the bot won't go through the backlog on its own.)
@lwhsu: I think it makes more sense to just run dist_check on FreeBSD.
Sidenote: some of the kyua tests are crashing on Jenkins, btw. Do they occur on the cirrus runs?
@lwhsu would you mind resubmitting this PR to https://github.com/freebsd/kyua , now that we've forked the project?
https://github.com/freebsd/kyua/pull/1
This has merged with https://github.com/jmmv/kyua/pull/208
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.
. If the bot doesn't comment, it means it doesn't think anything has changed.
ℹ️ Googlers: Go here for more info.
This is not covering all the things in Travis-CI, but should be a good start for testing on BSD systems.