Re: [PATCH v2 0/2] Rework iotests finding

2020-03-25 Thread Vladimir Sementsov-Ogievskiy
25.03.2020 16:08, Eric Blake wrote: On 3/25/20 5:21 AM, Vladimir Sementsov-Ogievskiy wrote: Hi all! When sending iotests to upstream or do patch porting from one branch to another we very often have to resolve conflicts in group file, as many absolutely independent features are intersecting by

Re: [PATCH v2 0/2] Rework iotests finding

2020-03-25 Thread Eric Blake
On 3/25/20 5:21 AM, Vladimir Sementsov-Ogievskiy wrote: Hi all! When sending iotests to upstream or do patch porting from one branch to another we very often have to resolve conflicts in group file, as many absolutely independent features are intersecting by this file. These conflicts are simple

Re: [PATCH v2 0/2] Rework iotests finding

2020-03-25 Thread Vladimir Sementsov-Ogievskiy
25.03.2020 14:56, no-re...@patchew.org wrote: Patchew URL: https://patchew.org/QEMU/20200325102131.23270-1-vsement...@virtuozzo.com/ Hi, This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can pro

Re: [PATCH v2 0/2] Rework iotests finding

2020-03-25 Thread no-reply
Patchew URL: https://patchew.org/QEMU/20200325102131.23270-1-vsement...@virtuozzo.com/ Hi, This series failed the docker-quick@centos7 build test. Please find the testing commands and their output below. If you have Docker installed, you can probably reproduce it locally. === TEST SCRIPT BEG

[PATCH v2 0/2] Rework iotests finding

2020-03-25 Thread Vladimir Sementsov-Ogievskiy
Hi all! When sending iotests to upstream or do patch porting from one branch to another we very often have to resolve conflicts in group file, as many absolutely independent features are intersecting by this file. These conflicts are simple, but imagine how much time we all have already spent on r