summary refs log tree commit diff stats
path: root/gitlab/issues/target_missing/host_missing/accel_missing/1884.toml
diff options
context:
space:
mode:
Diffstat (limited to 'gitlab/issues/target_missing/host_missing/accel_missing/1884.toml')
-rw-r--r--gitlab/issues/target_missing/host_missing/accel_missing/1884.toml22
1 files changed, 22 insertions, 0 deletions
diff --git a/gitlab/issues/target_missing/host_missing/accel_missing/1884.toml b/gitlab/issues/target_missing/host_missing/accel_missing/1884.toml
new file mode 100644
index 000000000..00032fe4a
--- /dev/null
+++ b/gitlab/issues/target_missing/host_missing/accel_missing/1884.toml
@@ -0,0 +1,22 @@
+id = 1884
+title = "avocado-system-* CI jobs are unreliable"
+state = "closed"
+created_at = "2023-09-12T14:43:13.307Z"
+closed_at = "2024-01-11T17:02:11.158Z"
+labels = ["CI", "flaky-ci", "kind::Bug"]
+url = "https://gitlab.com/qemu-project/qemu/-/issues/1884"
+host-os = "n/a"
+host-arch = "n/a"
+qemu-version = "n/a"
+guest-os = "n/a"
+guest-arch = "n/a"
+description = """The avocado-system-* CI jobs fail randomly:
+https://gitlab.com/qemu-project/qemu/-/jobs/5058610614  
+https://gitlab.com/qemu-project/qemu/-/jobs/5058610654  
+https://gitlab.com/qemu-project/qemu/-/jobs/5030428571  
+
+I don't know how to interpret the test output. Until these CI jobs pass reliably it won't be possible for me to identify when a subtest that is actually healthy/reliable breaks.
+
+Please take a look at the logs and fix or remove unreliable test cases."""
+reproduce = "n/a"
+additional = "n/a"