Re: [PATCH v2 0/5] Move remaining x86 Travis jobs to the gitlab-CI
Will do. On Wed, 10 Feb 2021, 05:44 Thomas Huth, wrote: > On 09/02/2021 21.37, Alex Bennée wrote: > > > > Thomas Huth writes: > > > >> Since Travis changed their policies, travis-ci.org will soon become > >> completely useless for the QEMU project. We should now really make sure > >> that we move the remaining tests as good as possible to the gitlab-CI > >> instead. > > > > Queued to testing/next, thanks. > > Thanks, but please unqueue them again, I still want to send a v3 to > address > your comment on the -fsanitize=undefined patch... and I also noticed that > the gprof/gcov job runs very long and sometimes hits the 1h time limit, so > I > need to revisit the set of target architectures there... > > Thomas > >
Re: [PATCH v2 0/5] Move remaining x86 Travis jobs to the gitlab-CI
On 09/02/2021 21.37, Alex Bennée wrote: Thomas Huth writes: Since Travis changed their policies, travis-ci.org will soon become completely useless for the QEMU project. We should now really make sure that we move the remaining tests as good as possible to the gitlab-CI instead. Queued to testing/next, thanks. Thanks, but please unqueue them again, I still want to send a v3 to address your comment on the -fsanitize=undefined patch... and I also noticed that the gprof/gcov job runs very long and sometimes hits the 1h time limit, so I need to revisit the set of target architectures there... Thomas
Re: [PATCH v2 0/5] Move remaining x86 Travis jobs to the gitlab-CI
Thomas Huth writes: > Since Travis changed their policies, travis-ci.org will soon become > completely useless for the QEMU project. We should now really make sure > that we move the remaining tests as good as possible to the gitlab-CI > instead. Queued to testing/next, thanks. -- Alex Bennée
[PATCH v2 0/5] Move remaining x86 Travis jobs to the gitlab-CI
Since Travis changed their policies, travis-ci.org will soon become completely useless for the QEMU project. We should now really make sure that we move the remaining tests as good as possible to the gitlab-CI instead. v2: - Run "make check" in the gprof/gcov test - Make sure that we run at least one test with --enable-debug - Reworked the thread sanitizer patch to use --enable-tsan + clang now Philippe Mathieu-Daudé (1): travis.yml: Move gprof/gcov test across to gitlab Thomas Huth (4): travis.yml: Move the -fsanitize=undefined test to the gitlab-CI travis.yml: Move the --enable-modules test to the gitlab-CI travis.yml: (Re-)move the --enable-debug jobs travis.yml: Move the -fsanitize=thread testing to the gitlab-CI .gitlab-ci.yml | 38 ++- .travis.yml| 111 - MAINTAINERS| 2 +- scripts/{travis => ci}/coverage-summary.sh | 2 +- tests/docker/dockerfiles/ubuntu2004.docker | 2 + 5 files changed, 39 insertions(+), 116 deletions(-) rename scripts/{travis => ci}/coverage-summary.sh (92%) -- 2.27.0