* check-python-tox failures
@ 2021-12-23 4:11 Richard Henderson
2021-12-30 0:03 ` Philippe Mathieu-Daudé
0 siblings, 1 reply; 3+ messages in thread
From: Richard Henderson @ 2021-12-23 4:11 UTC (permalink / raw)
To: John Snow; +Cc: qemu-devel
Hi John,
This test has been failing for quite a while. While it is allowed to fail, can we either
fix this or disable it, to allow the ci to go proper green?
r~
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: check-python-tox failures
2021-12-23 4:11 check-python-tox failures Richard Henderson
@ 2021-12-30 0:03 ` Philippe Mathieu-Daudé
2022-01-03 5:43 ` John Snow
0 siblings, 1 reply; 3+ messages in thread
From: Philippe Mathieu-Daudé @ 2021-12-30 0:03 UTC (permalink / raw)
To: Richard Henderson, John Snow; +Cc: Thomas Huth, qemu-devel
On 12/23/21 05:11, Richard Henderson wrote:
> Hi John,
>
> This test has been failing for quite a while. While it is allowed to
> fail, can we either fix this or disable it, to allow the ci to go proper
> green?
This job not only fails on the mainstream pipelines, but also on
all forks recently rebased. This is very annoying, I am in favor
of disabling the job until someone figure out what is wrong.
Phil.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: check-python-tox failures
2021-12-30 0:03 ` Philippe Mathieu-Daudé
@ 2022-01-03 5:43 ` John Snow
0 siblings, 0 replies; 3+ messages in thread
From: John Snow @ 2022-01-03 5:43 UTC (permalink / raw)
To: Philippe Mathieu-Daudé
Cc: Thomas Huth, Richard Henderson, qemu-devel, Cleber Rosa
[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]
On Wed, Dec 29, 2021 at 7:03 PM Philippe Mathieu-Daudé <philmd@redhat.com>
wrote:
> On 12/23/21 05:11, Richard Henderson wrote:
> > Hi John,
> >
> > This test has been failing for quite a while. While it is allowed to
> > fail, can we either fix this or disable it, to allow the ci to go proper
> > green?
>
> This job not only fails on the mainstream pipelines, but also on
> all forks recently rebased. This is very annoying, I am in favor
> of disabling the job until someone figure out what is wrong.
>
> Phil.
>
>
I've been away on holiday, and will be away for another week.
Looks like a few dependencies were updated in the python ecosystem and
broke a few things. I tried to fix it in a few hurried minutes, but ... it
looks pretty broken:
(33/33) tests/pylint.sh: FAIL: Exited with status: '1', stdout:
"************* \nqemu/__init__.py:1:0: F0010: error while code parsing:
Unable to load file qemu/__init__.py:\n[Errno 2] No such file or directory:
'qemu/__init__.py' (parse-error)\n", stderr: "*************
\nqemu/__init_... (0.54 s)
I am not sure why on god's green earth Pylint has decided it doesn't know
how to import namespaced modules anymore. I probably won't be able to fix
this until next week, so just disable it for now and I'll fix it when I get
back.
--js.
(ps: attempted fix here https://gitlab.com/jsnow/qemu/-/pipelines/440208449
but there seems to be something very wrong with pylint in the tox
environment -- I suspect a dependency of pylint's was updated and is
breaking things. I'll have to identify which one it is and update the
package reqs to exclude it, but ATM I have no idea which it is.)
(pps, Cleber, what happened to the avocado output here? It's not showing
error logs from the failed tests anymore. Did avocado update and break
these options?)
[-- Attachment #2: Type: text/html, Size: 2437 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-01-03 5:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-23 4:11 check-python-tox failures Richard Henderson
2021-12-30 0:03 ` Philippe Mathieu-Daudé
2022-01-03 5:43 ` John Snow
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.