[PULL,0/16] Python (acceptance tests) queue, 2019-10-28
mbox

Message ID 20191028235002.17691-1-crosa@redhat.com
State New
Headers show

Pull-request

git://github.com/clebergnu/qemu.git tags/python-next-pull-request

Message

Cleber Rosa Oct. 28, 2019, 11:49 p.m. UTC
The following changes since commit aaffb853359829a37daaf883c773e8320b55c723:

  Merge remote-tracking branch 'remotes/maxreitz/tags/pull-block-2019-10-28' into staging (2019-10-28 14:40:01 +0000)

are available in the Git repository at:

  git://github.com/clebergnu/qemu.git tags/python-next-pull-request

for you to fetch changes up to efdb45bfd72745038909dfd1e970a827cb8d5d7e:

  tests/boot_linux_console: Run BusyBox on 5KEc 64-bit cpu (2019-10-28 19:04:04 -0400)

----------------------------------------------------------------

Cleber Rosa (4):
  MAINTAINERS: update location of Python libraries
  Acceptance tests: work around socket dir
  Python libs: close console sockets before shutting down the VMs
  Acceptance tests: refactor wait_for_console_pattern

Philippe Mathieu-Daudé (12):
  tests/acceptance: Fix wait_for_console_pattern() hangs
  tests/acceptance: Send <carriage return> on serial lines
  tests/acceptance: Refactor exec_command_and_wait_for_pattern()
  tests/acceptance: Add test that boots the HelenOS microkernel on Leon3
  .travis.yml: Let the avocado job run the Leon3 test
  tests/acceptance: Add test that runs NetBSD 4.0 installer on PRep/40p
  tests/acceptance: Test OpenBIOS on the PReP/40p
  .travis.yml: Let the avocado job run the 40p tests
  tests/boot_linux_console: Use Avocado archive::gzip_uncompress()
  tests/boot_linux_console: Add a test for the Raspberry Pi 2
  tests/boot_linux_console: Add initrd test for the Exynos4210
  tests/boot_linux_console: Run BusyBox on 5KEc 64-bit cpu

 .travis.yml                               |   2 +-
 MAINTAINERS                               |   4 +-
 python/qemu/machine.py                    |  11 +-
 tests/acceptance/avocado_qemu/__init__.py |  48 ++++++-
 tests/acceptance/boot_linux_console.py    | 167 +++++++++++++++++-----
 tests/acceptance/linux_ssh_mips_malta.py  |  18 +--
 tests/acceptance/machine_sparc_leon3.py   |  34 +++++
 tests/acceptance/ppc_prep_40p.py          |  82 +++++++++++
 8 files changed, 308 insertions(+), 58 deletions(-)
 create mode 100644 tests/acceptance/machine_sparc_leon3.py
 create mode 100644 tests/acceptance/ppc_prep_40p.py

Comments

Peter Maydell Oct. 29, 2019, 9:13 p.m. UTC | #1
On Mon, 28 Oct 2019 at 23:50, Cleber Rosa <crosa@redhat.com> wrote:
>
> The following changes since commit aaffb853359829a37daaf883c773e8320b55c723:
>
>   Merge remote-tracking branch 'remotes/maxreitz/tags/pull-block-2019-10-28' into staging (2019-10-28 14:40:01 +0000)
>
> are available in the Git repository at:
>
>   git://github.com/clebergnu/qemu.git tags/python-next-pull-request
>
> for you to fetch changes up to efdb45bfd72745038909dfd1e970a827cb8d5d7e:
>
>   tests/boot_linux_console: Run BusyBox on 5KEc 64-bit cpu (2019-10-28 19:04:04 -0400)
>
> ----------------------------------------------------------------

Hi; unless my scripts are driving gpg wrong, this seems to
have been signed with an expired gpg key:

gpg: Signature made Mon 28 Oct 2019 23:43:11 GMT
gpg:                using RSA key 7ABB96EB8B46B94D5E0FE9BB657E8D33A5F209F3
gpg: Good signature from "Cleber Rosa <crosa@redhat.com>" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: 7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3


thanks
-- PMM
Cleber Rosa Oct. 29, 2019, 9:51 p.m. UTC | #2
On Tue, Oct 29, 2019 at 09:13:45PM +0000, Peter Maydell wrote:
> On Mon, 28 Oct 2019 at 23:50, Cleber Rosa <crosa@redhat.com> wrote:
> >
> > The following changes since commit aaffb853359829a37daaf883c773e8320b55c723:
> >
> >   Merge remote-tracking branch 'remotes/maxreitz/tags/pull-block-2019-10-28' into staging (2019-10-28 14:40:01 +0000)
> >
> > are available in the Git repository at:
> >
> >   git://github.com/clebergnu/qemu.git tags/python-next-pull-request
> >
> > for you to fetch changes up to efdb45bfd72745038909dfd1e970a827cb8d5d7e:
> >
> >   tests/boot_linux_console: Run BusyBox on 5KEc 64-bit cpu (2019-10-28 19:04:04 -0400)
> >
> > ----------------------------------------------------------------
> 
> Hi; unless my scripts are driving gpg wrong, this seems to
> have been signed with an expired gpg key:
> 
> gpg: Signature made Mon 28 Oct 2019 23:43:11 GMT
> gpg:                using RSA key 7ABB96EB8B46B94D5E0FE9BB657E8D33A5F209F3
> gpg: Good signature from "Cleber Rosa <crosa@redhat.com>" [expired]
> gpg: Note: This key has expired!
> Primary key fingerprint: 7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3
> 
> 
> thanks
> -- PMM

Hi Peter,

Nothing wrong with your scripts.  I updated my key about a week ago,
but I'm almost certain that the key servers that I sent it to was
acting funky.

After some further pushes, I see it on:

  http://keys.gnupg.net/pks/lookup?op=vindex&fingerprint=on&search=0x657E8D33A5F209F3

---

Search results for '0x657e8d33a5f209f3'
Type bits/keyID     cr. time   exp time   key expir
pub  4096R/A5F209F3 2014-10-16            
	 Fingerprint=7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3 

uid Cleber Rosa <crosa@redhat.com>
sig  sig3  A5F209F3 2014-10-16 __________ 2019-10-15 [selfsig]
sig  sig   7657B59A 2014-10-16 __________ __________ Rudá Moura <rmoura@redhat.com>
sig  sig   2527436A 2019-03-05 __________ __________ Eric Blake <eblake@redhat.com>
sig  sig   984DC5A6 2019-03-06 __________ __________ Eduardo Habkost <ehabkost@redhat.com>
sig  sig3  96799EF4 2019-03-06 __________ __________ Bandan Das <bsd@redhat.com>
sig  sig3  A5F209F3 2019-10-22 __________ 2024-10-20 [selfsig]

sub  4096R/5B75AD33 2014-10-16            
sig sbind  A5F209F3 2014-10-16 __________ 2019-10-15 []
sig sbind  A5F209F3 2019-10-22 __________ 2024-10-20 []

---

And with a fresh environment:

  $ podman run --rm -ti fedora:30
  [root@afba6c046a22 /]# gpg --search-key 657E8D33A5F209F3
  gpg: directory '/root/.gnupg' created
  gpg: keybox '/root/.gnupg/pubring.kbx' created
  gpg: data source: https://51.38.91.189:443
  (1)     Cleber Rosa <crosa@redhat.com>
            4096 bit RSA key 657E8D33A5F209F3, created: 2014-10-16, expires: 2024-10-20
  Keys 1-1 of 1 for "657E8D33A5F209F3".  Enter number(s), N)ext, or Q)uit > 1
  gpg: key 657E8D33A5F209F3: 4 signatures not checked due to missing keys
  gpg: /root/.gnupg/trustdb.gpg: trustdb created
  gpg: key 657E8D33A5F209F3: public key "Cleber Rosa <crosa@redhat.com>" imported
  gpg: no ultimately trusted keys found
  gpg: Total number processed: 1
  gpg:               imported: 1

---

So I guess "all" you'd need is a refresh.  Sorry for the inconvenience,
and let me know if there's anything else I can do.

- Cleber.
Cleber Rosa Oct. 29, 2019, 9:58 p.m. UTC | #3
On Tue, Oct 29, 2019 at 05:51:28PM -0400, Cleber Rosa wrote:
> On Tue, Oct 29, 2019 at 09:13:45PM +0000, Peter Maydell wrote:
> > On Mon, 28 Oct 2019 at 23:50, Cleber Rosa <crosa@redhat.com> wrote:
> > >
> > > The following changes since commit aaffb853359829a37daaf883c773e8320b55c723:
> > >
> > >   Merge remote-tracking branch 'remotes/maxreitz/tags/pull-block-2019-10-28' into staging (2019-10-28 14:40:01 +0000)
> > >
> > > are available in the Git repository at:
> > >
> > >   git://github.com/clebergnu/qemu.git tags/python-next-pull-request
> > >
> > > for you to fetch changes up to efdb45bfd72745038909dfd1e970a827cb8d5d7e:
> > >
> > >   tests/boot_linux_console: Run BusyBox on 5KEc 64-bit cpu (2019-10-28 19:04:04 -0400)
> > >
> > > ----------------------------------------------------------------
> > 
> > Hi; unless my scripts are driving gpg wrong, this seems to
> > have been signed with an expired gpg key:
> > 
> > gpg: Signature made Mon 28 Oct 2019 23:43:11 GMT
> > gpg:                using RSA key 7ABB96EB8B46B94D5E0FE9BB657E8D33A5F209F3
> > gpg: Good signature from "Cleber Rosa <crosa@redhat.com>" [expired]
> > gpg: Note: This key has expired!
> > Primary key fingerprint: 7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3
> > 
> > 
> > thanks
> > -- PMM
> 
> Hi Peter,
> 
> Nothing wrong with your scripts.  I updated my key about a week ago,
> but I'm almost certain that the key servers that I sent it to was
> acting funky.
> 
> After some further pushes, I see it on:
> 
>   http://keys.gnupg.net/pks/lookup?op=vindex&fingerprint=on&search=0x657E8D33A5F209F3
> 
> ---
> 
> Search results for '0x657e8d33a5f209f3'
> Type bits/keyID     cr. time   exp time   key expir
> pub  4096R/A5F209F3 2014-10-16            
> 	 Fingerprint=7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3 
> 
> uid Cleber Rosa <crosa@redhat.com>
> sig  sig3  A5F209F3 2014-10-16 __________ 2019-10-15 [selfsig]
> sig  sig   7657B59A 2014-10-16 __________ __________ Rudá Moura <rmoura@redhat.com>
> sig  sig   2527436A 2019-03-05 __________ __________ Eric Blake <eblake@redhat.com>
> sig  sig   984DC5A6 2019-03-06 __________ __________ Eduardo Habkost <ehabkost@redhat.com>
> sig  sig3  96799EF4 2019-03-06 __________ __________ Bandan Das <bsd@redhat.com>
> sig  sig3  A5F209F3 2019-10-22 __________ 2024-10-20 [selfsig]
> 
> sub  4096R/5B75AD33 2014-10-16            
> sig sbind  A5F209F3 2014-10-16 __________ 2019-10-15 []
> sig sbind  A5F209F3 2019-10-22 __________ 2024-10-20 []
> 
> ---
> 
> And with a fresh environment:
> 
>   $ podman run --rm -ti fedora:30
>   [root@afba6c046a22 /]# gpg --search-key 657E8D33A5F209F3
>   gpg: directory '/root/.gnupg' created
>   gpg: keybox '/root/.gnupg/pubring.kbx' created
>   gpg: data source: https://51.38.91.189:443
>   (1)     Cleber Rosa <crosa@redhat.com>
>             4096 bit RSA key 657E8D33A5F209F3, created: 2014-10-16, expires: 2024-10-20
>   Keys 1-1 of 1 for "657E8D33A5F209F3".  Enter number(s), N)ext, or Q)uit > 1
>   gpg: key 657E8D33A5F209F3: 4 signatures not checked due to missing keys
>   gpg: /root/.gnupg/trustdb.gpg: trustdb created
>   gpg: key 657E8D33A5F209F3: public key "Cleber Rosa <crosa@redhat.com>" imported
>   gpg: no ultimately trusted keys found
>   gpg: Total number processed: 1
>   gpg:               imported: 1
> 
> ---
> 
> So I guess "all" you'd need is a refresh.  Sorry for the inconvenience,
> and let me know if there's anything else I can do.
> 
> - Cleber.

OK, so now I don't see the updated key anymore on the public key servers,
which confirms that I'm doing something wrong.

I'm trying to fix that situation.  Sorry for the inconvenience again.

- Cleber.
Cleber Rosa Oct. 29, 2019, 11:40 p.m. UTC | #4
On Tue, Oct 29, 2019 at 05:58:13PM -0400, Cleber Rosa wrote:
> On Tue, Oct 29, 2019 at 05:51:28PM -0400, Cleber Rosa wrote:
> > On Tue, Oct 29, 2019 at 09:13:45PM +0000, Peter Maydell wrote:
> > > On Mon, 28 Oct 2019 at 23:50, Cleber Rosa <crosa@redhat.com> wrote:
> > > >
> > > > The following changes since commit aaffb853359829a37daaf883c773e8320b55c723:
> > > >
> > > >   Merge remote-tracking branch 'remotes/maxreitz/tags/pull-block-2019-10-28' into staging (2019-10-28 14:40:01 +0000)
> > > >
> > > > are available in the Git repository at:
> > > >
> > > >   git://github.com/clebergnu/qemu.git tags/python-next-pull-request
> > > >
> > > > for you to fetch changes up to efdb45bfd72745038909dfd1e970a827cb8d5d7e:
> > > >
> > > >   tests/boot_linux_console: Run BusyBox on 5KEc 64-bit cpu (2019-10-28 19:04:04 -0400)
> > > >
> > > > ----------------------------------------------------------------
> > > 
> > > Hi; unless my scripts are driving gpg wrong, this seems to
> > > have been signed with an expired gpg key:
> > > 
> > > gpg: Signature made Mon 28 Oct 2019 23:43:11 GMT
> > > gpg:                using RSA key 7ABB96EB8B46B94D5E0FE9BB657E8D33A5F209F3
> > > gpg: Good signature from "Cleber Rosa <crosa@redhat.com>" [expired]
> > > gpg: Note: This key has expired!
> > > Primary key fingerprint: 7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3
> > > 
> > > 
> > > thanks
> > > -- PMM
> > 
> > Hi Peter,
> > 
> > Nothing wrong with your scripts.  I updated my key about a week ago,
> > but I'm almost certain that the key servers that I sent it to was
> > acting funky.
> > 
> > After some further pushes, I see it on:
> > 
> >   http://keys.gnupg.net/pks/lookup?op=vindex&fingerprint=on&search=0x657E8D33A5F209F3
> > 
> > ---
> > 
> > Search results for '0x657e8d33a5f209f3'
> > Type bits/keyID     cr. time   exp time   key expir
> > pub  4096R/A5F209F3 2014-10-16            
> > 	 Fingerprint=7ABB 96EB 8B46 B94D 5E0F  E9BB 657E 8D33 A5F2 09F3 
> > 
> > uid Cleber Rosa <crosa@redhat.com>
> > sig  sig3  A5F209F3 2014-10-16 __________ 2019-10-15 [selfsig]
> > sig  sig   7657B59A 2014-10-16 __________ __________ Rudá Moura <rmoura@redhat.com>
> > sig  sig   2527436A 2019-03-05 __________ __________ Eric Blake <eblake@redhat.com>
> > sig  sig   984DC5A6 2019-03-06 __________ __________ Eduardo Habkost <ehabkost@redhat.com>
> > sig  sig3  96799EF4 2019-03-06 __________ __________ Bandan Das <bsd@redhat.com>
> > sig  sig3  A5F209F3 2019-10-22 __________ 2024-10-20 [selfsig]
> > 
> > sub  4096R/5B75AD33 2014-10-16            
> > sig sbind  A5F209F3 2014-10-16 __________ 2019-10-15 []
> > sig sbind  A5F209F3 2019-10-22 __________ 2024-10-20 []
> > 
> > ---
> > 
> > And with a fresh environment:
> > 
> >   $ podman run --rm -ti fedora:30
> >   [root@afba6c046a22 /]# gpg --search-key 657E8D33A5F209F3
> >   gpg: directory '/root/.gnupg' created
> >   gpg: keybox '/root/.gnupg/pubring.kbx' created
> >   gpg: data source: https://51.38.91.189:443
> >   (1)     Cleber Rosa <crosa@redhat.com>
> >             4096 bit RSA key 657E8D33A5F209F3, created: 2014-10-16, expires: 2024-10-20
> >   Keys 1-1 of 1 for "657E8D33A5F209F3".  Enter number(s), N)ext, or Q)uit > 1
> >   gpg: key 657E8D33A5F209F3: 4 signatures not checked due to missing keys
> >   gpg: /root/.gnupg/trustdb.gpg: trustdb created
> >   gpg: key 657E8D33A5F209F3: public key "Cleber Rosa <crosa@redhat.com>" imported
> >   gpg: no ultimately trusted keys found
> >   gpg: Total number processed: 1
> >   gpg:               imported: 1
> > 
> > ---
> > 
> > So I guess "all" you'd need is a refresh.  Sorry for the inconvenience,
> > and let me know if there's anything else I can do.
> > 
> > - Cleber.
> 
> OK, so now I don't see the updated key anymore on the public key servers,
> which confirms that I'm doing something wrong.
> 
> I'm trying to fix that situation.  Sorry for the inconvenience again.
> 
> - Cleber.

I'm now getting the updated key on every single server I've tried.

Any further feedback/request is highly appreciated.

Thanks,
- Cleber.
Peter Maydell Oct. 30, 2019, 2:10 p.m. UTC | #5
On Tue, 29 Oct 2019 at 23:40, Cleber Rosa <crosa@redhat.com> wrote:
>
> I'm now getting the updated key on every single server I've tried.
>
> Any further feedback/request is highly appreciated.

Yep, I was able to pull the updated key.


Applied, thanks.

Please update the changelog at https://wiki.qemu.org/ChangeLog/4.2
for any user-visible changes.

-- PMM