Re: [PULL 00/10] Block jobs & NBD patches

[Vladimir Sementsov-Ogievskiy]

On 6/14/22 21:05, Richard Henderson wrote:
> On 6/14/22 03:29, Vladimir Sementsov-Ogievskiy wrote:
> > The following changes since commit debd0753663bc89c86f5462a53268f2e3f680f60:
> >
> >    Merge tag 'pull-testing-next-140622-1' of https://github.com/stsquad/qemu 
> > into staging (2022-06-13 21:10:57 -0700)
> >
> > are available in the Git repository at:
> >
> >    https://gitlab.com/vsementsov/qemu.git tags/pull-block-2022-06-14
> >
> > for you to fetch changes up to 5aef6747a250f545ff53ba7e1a3ed7a3d166011a:
> >
> >    MAINTAINERS: update Vladimir's address and repositories (2022-06-14 12:51:48 
> > +0300)
> >
> > ----------------------------------------------------------------
> > Block jobs & NBD patches
> >
> > - add new options for copy-before-write filter
> > - new trace points for NBD
> > - prefer unsigned type for some 'in_flight' fields
> > - update my addresses in MAINTAINERS (already in Stefan's tree, but
> >    I think it's OK to send it with this PULL)
> >
> >
> > Note also, that I've recently updated my pgp key with new address and
> > new expire time.
> > Updated key is here: 
> > https://keys.openpgp.org/search?q=vsementsov%40yandex-team.ru
>
> This introduces or exposes new timeouts:
>
> https://gitlab.com/qemu-project/qemu/-/pipelines/563590515/failures

Not obvious from logs, which iotest hangs. But excluding iotests that passed, 
it becomes obvious that problem is in copy-before-write iotest, which is added 
and then updated in the series..

And most probably, that's a new timeout feature, that doesn't work (patches 
04-07).. It works for me locally still. I'd be glad if someone could look it 
through.

I think, for now, I'll just resend a pull request without these 4 patches.

Also, could/should I run all these test pipelines on gitlab by hand before 
sending a PULL request? Or can I rerun them on my qemu fork for debugging?


--
Best regards,
Vladimir