Message ID | 20200731094607.15204-1-frankja@linux.ibm.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On 31/07/20 11:45, Janosch Frank wrote:
> https://github.com/frankjaa/kvm-unit-tests.git tags/s390x-2020-31-07
Pulled, thanks. FWIW you may want to gitlab in order to get the CI.
Paolo
On 7/31/20 12:31 PM, Paolo Bonzini wrote: > On 31/07/20 11:45, Janosch Frank wrote: >> https://github.com/frankjaa/kvm-unit-tests.git tags/s390x-2020-31-07 > > Pulled, thanks. FWIW you may want to gitlab in order to get the CI. > > Paolo > Hey Paolo, that repository is hooked up to travis already: https://travis-ci.com/github/frankjaa/kvm-unit-tests/builds/177931162 I'll consider it if it has any benefit. @Thomas: Are there differences in the CI?
On 31/07/2020 13.31, Janosch Frank wrote: > On 7/31/20 12:31 PM, Paolo Bonzini wrote: >> On 31/07/20 11:45, Janosch Frank wrote: >>> https://github.com/frankjaa/kvm-unit-tests.git tags/s390x-2020-31-07 >> >> Pulled, thanks. FWIW you may want to gitlab in order to get the CI. >> >> Paolo >> > > Hey Paolo, that repository is hooked up to travis already: > https://travis-ci.com/github/frankjaa/kvm-unit-tests/builds/177931162 > > I'll consider it if it has any benefit. > @Thomas: Are there differences in the CI? Not that much, you get a good build test coverage with both. Travis uses real (nested) KVM tests, but the compiler and QEMU versions are a little bit backlevel (still using Ubuntu bionic). Gitlab-CI uses newer versions (thanks to Fedora 32), but there is no KVM support here, so the tests run with TCG only (I'm thinking of adding the cirrus-run script to the Gitlab-CI, maybe we could get some KVM-coverage that way there, too, but that will certainly take some time to figure it out). Thomas
On 7/31/20 2:09 PM, Thomas Huth wrote: > On 31/07/2020 13.31, Janosch Frank wrote: >> On 7/31/20 12:31 PM, Paolo Bonzini wrote: >>> On 31/07/20 11:45, Janosch Frank wrote: >>>> https://github.com/frankjaa/kvm-unit-tests.git tags/s390x-2020-31-07 >>> >>> Pulled, thanks. FWIW you may want to gitlab in order to get the CI. >>> >>> Paolo >>> >> >> Hey Paolo, that repository is hooked up to travis already: >> https://travis-ci.com/github/frankjaa/kvm-unit-tests/builds/177931162 >> >> I'll consider it if it has any benefit. >> @Thomas: Are there differences in the CI? > > Not that much, you get a good build test coverage with both. Travis uses > real (nested) KVM tests, but the compiler and QEMU versions are a little > bit backlevel (still using Ubuntu bionic). Gitlab-CI uses newer versions > (thanks to Fedora 32), but there is no KVM support here, so the tests > run with TCG only (I'm thinking of adding the cirrus-run script to the > Gitlab-CI, maybe we could get some KVM-coverage that way there, too, but > that will certainly take some time to figure it out). > > Thomas > Thanks for the answer! For now I'll stay with github/travis until I have a real reason to move over. Maybe if the qemu CI run doesn't take ~2h on gitlab I'll start considering moving.