qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
	qemu-block@nongnu.org, "John Snow" <jsnow@redhat.com>,
	qemu-devel@nongnu.org, "Max Reitz" <mreitz@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v3 0/6] Enable more iotests during "make check-block"
Date: Tue, 22 Oct 2019 13:46:50 +0200	[thread overview]
Message-ID: <622d7844-c532-2de8-f39d-ba81082ed5d2@redhat.com> (raw)
In-Reply-To: <87ftjlvwjd.fsf@linaro.org>

On 22/10/2019 13.39, Alex Bennée wrote:
> 
> Thomas Huth <thuth@redhat.com> writes:
> 
>> On 22/10/2019 09.21, Thomas Huth wrote:
>>> As discussed here:
>>>
>>>  https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg00697.html
>>>
>>> and here:
>>>
>>>  https://lists.gnu.org/archive/html/qemu-devel/2019-10/msg01388.html
>>>
>>> it would be good to have some more valuable iotests enabled in the
>>> "auto" group to get better iotest coverage during "make check".
>>>
>>> And once Max' "iotests: Add and use $SOCK_DIR" patch series has been
>>> merged, we can indeed enable these Python-based tests, too.
>>
>> Oh well, some Travis jobs are now running too long and hit the 50
>> minutes limit:
>>
>>  https://travis-ci.com/huth/qemu/jobs/248158477
>>
>> ... so we either might need to remove some other iotests from the "auto"
>> group again, or change the Travis jobs to include less targets...
>>
>> That "clang + sanitizer" job was already running 45 minutes before my
>> change, so it was already close to the limit. So I'd suggest to change
>> it to include less targets. Opinions?
> 
> Which one is clang with sanitizers? I think we only build softmmu for
> gcc + sanitizer at the moment.

I meant this one here:

    - env:
        - CONFIG="--target-list=${MAIN_SOFTMMU_TARGETS} "
      compiler: clang
      before_script:
        - ./configure ${CONFIG} --extra-cflags="-fsanitize=undefined
-Werror" || { cat config.log && exit 1; }

 Thomas



  reply	other threads:[~2019-10-22 11:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22  7:21 [PATCH v3 0/6] Enable more iotests during "make check-block" Thomas Huth
2019-10-22  7:21 ` [PATCH v3 1/6] iotests: remove 'linux' from default supported platforms Thomas Huth
2019-10-22  7:21 ` [PATCH v3 2/6] iotests: Test 041 only works on certain systems Thomas Huth
2019-10-22  7:21 ` [PATCH v3 3/6] iotests: Test 183 does not work on macOS and OpenBSD Thomas Huth
2019-10-22  7:21 ` [PATCH v3 4/6] iotests: Skip "make check-block" if QEMU does not support virtio-blk Thomas Huth
2019-10-30 11:21   ` Max Reitz
2019-11-11 14:02     ` Thomas Huth
2019-11-11 16:10       ` Max Reitz
2019-10-22  7:21 ` [PATCH v3 5/6] iotests: Enable more tests in the 'auto' group to improve test coverage Thomas Huth
2019-10-24 11:14   ` Alex Bennée
2019-11-27 14:11     ` Thomas Huth
2019-10-22  7:21 ` [PATCH v3 6/6] iotests: Remove 130 from the "auto" group Thomas Huth
2019-10-22  7:58 ` [PATCH v3 0/6] Enable more iotests during "make check-block" Thomas Huth
2019-10-22 11:39   ` Alex Bennée
2019-10-22 11:46     ` Thomas Huth [this message]
2019-10-22 13:09       ` Alex Bennée
2019-10-22 13:11 ` Alex Bennée
2019-10-22 13:39   ` Max Reitz
2019-10-22 13:48     ` Alex Bennée
2019-10-22 18:54       ` Thomas Huth
2019-10-22 21:16         ` Alex Bennée

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=622d7844-c532-2de8-f39d-ba81082ed5d2@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).