Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-27 Thread Eric Blake
On 4/25/19 5:24 AM, Thomas Huth wrote: >> Ok, thanks for the info. Looks like many tests are failing because qemu-io >> suddenly prints its program name in front of the error messages? E.g.: >> >> --- /tmp/qemu-test/src/tests/qemu-iotests/069.out2019-04-24 >> 16:52:31.0 + >> +++

Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-25 Thread Thomas Huth
On 25/04/2019 07.57, Thomas Huth wrote: > On 24/04/2019 22.42, Wainer dos Santos Moschetta wrote: >> Hi Thomas, >> >> >> On 04/24/2019 07:37 AM, Thomas Huth wrote: >>> People often forget to run the iotests before submitting patches or >>> pull requests - this is likely due to the fact that we do n

Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-24 Thread Thomas Huth
On 24/04/2019 22.42, Wainer dos Santos Moschetta wrote: > Hi Thomas, > > > On 04/24/2019 07:37 AM, Thomas Huth wrote: >> People often forget to run the iotests before submitting patches or >> pull requests - this is likely due to the fact that we do not run the >> tests during our mandatory "make

Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-24 Thread Wainer dos Santos Moschetta
Hi Thomas, On 04/24/2019 07:37 AM, Thomas Huth wrote: People often forget to run the iotests before submitting patches or pull requests - this is likely due to the fact that we do not run the tests during our mandatory "make check" tests yet. Now that we've got a new "ci" group of iotests that

Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-24 Thread Vladimir Sementsov-Ogievskiy
24.04.2019 15:13, Daniel P. Berrangé wrote: > On Wed, Apr 24, 2019 at 12:02:29PM +, Vladimir Sementsov-Ogievskiy wrote: >> 24.04.2019 13:59, Thomas Huth wrote: >>> On 24/04/2019 12.48, Daniel P. Berrangé wrote: On Wed, Apr 24, 2019 at 12:37:46PM +0200, Thomas Huth wrote: > People often

Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-24 Thread Daniel P . Berrangé
On Wed, Apr 24, 2019 at 12:02:29PM +, Vladimir Sementsov-Ogievskiy wrote: > 24.04.2019 13:59, Thomas Huth wrote: > > On 24/04/2019 12.48, Daniel P. Berrangé wrote: > >> On Wed, Apr 24, 2019 at 12:37:46PM +0200, Thomas Huth wrote: > >>> People often forget to run the iotests before submitting pa

Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-24 Thread Vladimir Sementsov-Ogievskiy
24.04.2019 13:59, Thomas Huth wrote: > On 24/04/2019 12.48, Daniel P. Berrangé wrote: >> On Wed, Apr 24, 2019 at 12:37:46PM +0200, Thomas Huth wrote: >>> People often forget to run the iotests before submitting patches or >>> pull requests - this is likely due to the fact that we do not run the >>>

Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-24 Thread Thomas Huth
On 24/04/2019 12.48, Daniel P. Berrangé wrote: > On Wed, Apr 24, 2019 at 12:37:46PM +0200, Thomas Huth wrote: >> People often forget to run the iotests before submitting patches or >> pull requests - this is likely due to the fact that we do not run the >> tests during our mandatory "make check" te

Re: [Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-24 Thread Daniel P . Berrangé
On Wed, Apr 24, 2019 at 12:37:46PM +0200, Thomas Huth wrote: > People often forget to run the iotests before submitting patches or > pull requests - this is likely due to the fact that we do not run the > tests during our mandatory "make check" tests yet. Now that we've got > a new "ci" group of io

[Qemu-devel] [PATCH 5/6] tests: Run the iotests during "make check" again

2019-04-24 Thread Thomas Huth
People often forget to run the iotests before submitting patches or pull requests - this is likely due to the fact that we do not run the tests during our mandatory "make check" tests yet. Now that we've got a new "ci" group of iotests that should be fine to run in every environ- ment, it should be