From: GitLab via <qemu-devel@nongnu.org>
Subject: QEMU | Pipeline #171708785 has failed for master | 1e0e0917
Date: Tue, 28 Jul 2020 16:51:26 +0000 [thread overview]
Message-ID: <5f20578e72fe2_78703fba576821fc55136b@sidekiq-catchall-05-sv-gprd.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 3181 bytes --]
Your pipeline has failed.
Project: QEMU ( https://gitlab.com/qemu-project/qemu )
Branch: master ( https://gitlab.com/qemu-project/qemu/-/commits/master )
Commit: 1e0e0917 ( https://gitlab.com/qemu-project/qemu/-/commit/1e0e0917e5df765575a72afd35a7183e65f505ac )
Commit Message: Merge remote-tracking branch 'remotes/mdroth/ta...
Commit Author: Peter Maydell ( https://gitlab.com/pm215 )
Pipeline #171708785 ( https://gitlab.com/qemu-project/qemu/-/pipelines/171708785 ) triggered by Alex Bennée ( https://gitlab.com/stsquad )
had 1 failed build.
Job #660048436 ( https://gitlab.com/qemu-project/qemu/-/jobs/660048436/raw )
Stage: build
Name: build-tcg-disabled
Trace: 192 ... [16:06:11] ...
192 ^[[32mpass ^[[0m [16:06:11] [16:06:11] 0s
194 ... [16:06:11] ...
194 ^[[32mpass ^[[0m [16:06:11] [16:06:12] 1s
197 ... [16:06:12] ...
197 ^[[1m^[[31mfail ^[[0m [16:06:12] [16:07:54] output mismatch (see 197.out.bad)
--- /builds/qemu-project/qemu/tests/qemu-iotests/197.out 2020-07-28 15:56:14.000000000 +0000
+++ /builds/qemu-project/qemu/build/tests/qemu-iotests/197.out.bad 2020-07-28 16:07:53.000000000 +0000
@@ -26,9 +26,9 @@
=== Partial final cluster ===
-Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1024
+qemu-img: TEST_DIR/t.IMGFMT: Invalid parameter 'compat'
read 1024/1024 bytes at offset 0
1 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
-1 KiB (0x400) bytes allocated at offset 0 bytes (0x0)
+4 GiB (0x100000000) bytes allocated at offset 0 bytes (0x0)
No errors were found on the image.
*** done
208 ... [16:07:54] ...
208 ^[[32mpass ^[[0m [16:07:54] [16:07:56] 2s
215 ... [16:07:56] ...
215 ^[[32mpass ^[[0m [16:07:56] [16:09:30] 93s
221 ... [16:09:30] ...
221 ^[[32mpass ^[[0m [16:09:30] [16:09:30] 0s
222 ... [16:09:30] ...
222 ^[[32mpass ^[[0m [16:09:30] [16:09:33] 3s
226 ... [16:09:33] ...
226 ^[[32mpass ^[[0m [16:09:33] [16:09:33] 0s
227 ... [16:09:33] ...
227 ^[[32mpass ^[[0m [16:09:33] [16:09:34] 1s
236 ... [16:09:34] ...
236 ^[[32mpass ^[[0m [16:09:34] [16:09:34] 0s
253 ... [16:09:34] ...
253 ^[[32mpass ^[[0m [16:09:34] [16:09:34] 0s
277 ... [16:09:34] ...
277 ^[[32mpass ^[[0m [16:09:34] [16:09:35] 1s
Failures: 197
Failed 1 of 47 iotests
section_end:1595952589:step_script
^[[0K^[[31;1mERROR: Job failed: exit code 1
^[[0;m
--
You're receiving this email because of your account on gitlab.com.
[-- Attachment #2: Type: text/html, Size: 17390 bytes --]
reply other threads:[~2020-07-28 16:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f20578e72fe2_78703fba576821fc55136b@sidekiq-catchall-05-sv-gprd.mail \
--to=qemu-devel@nongnu.org \
--cc=gitlab@mg.gitlab.com \
--cc=noreply@gitlab.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.