blob: a2642c62f158ea641e1dde4042974636de6d75b5 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
|
id = 1885
title = "mipsel malta machine is broken in avocado console tests"
state = "closed"
created_at = "2023-09-13T16:24:26.692Z"
closed_at = "2023-09-13T17:16:56.134Z"
labels = ["Closed::Duplicate", "kind::Bug"]
url = "https://gitlab.com/qemu-project/qemu/-/issues/1885"
host-os = "n/a"
host-arch = "n/a"
qemu-version = "n/a"
guest-os = "n/a"
guest-arch = "n/a"
description = """As noted in #1884 we see failures of the boot_linux_console.py test. Unlikely other avocado failures, these ones are consistent and reproduce locally with 100% success
```
./configure --target-list=mipsel-softmmu
make -j 20
cd build
./pyvenv/bin/python3 -B -m avocado --show=app run --job-results-dir=./tests/results -t arch:mipsel --failfast tests/avocado/boot_linux_console.py:BootLinuxConsole.test_mips_malta32el_nanomips_4k
```
This test will reliably fail with a timeout waiting for console output.
Attempting to run the QEMU command manually
```
$ ./qemu-system-mipsel -display none -vga none -machine malta -chardev stdio,id=console -serial chardev:console -cpu I7200 -no-reboot -kernel /home/berrange/src/virt/qemu/build/tests/results/job-2023-09-13T17.14-77de093/test-results/tmp_dir520smana/1-tests_avocado_boot_linux_console.py_BootLinuxConsole.test_mips_malta32el_nanomips_4kkernel -append 'printk.time=0 mem=256m@@0x0 console=ttyS0'
```
results in no serial console output at all.
IMHO either the MIPS malta machine has had a regression, or the kernel we're downloading for testing has had a regression."""
reproduce = "n/a"
additional = """"""
|