From: gspe <gspe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: qemu: datadir is not set, uefi support is broken
Date: Thu, 21 Jan 2021 22:02:24 +0100 [thread overview]
Message-ID: <20210121210224.0Miu-GNxUgzR5CPbpi-UzTW8oUfgp0FYXrjjhhUVwGY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27965@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 7313 bytes --]
New comment by gspe on void-packages repository
https://github.com/void-linux/void-packages/issues/27965#issuecomment-764939792
Comment:
I've used `"$XBPS_CHECK_PKGS" = full` option but it doesn't make any difference I still got errors during checks
this is pastebin of them https://pastebin.com/VUCnbbTY
This is just one of them in case of pastebin doesn't works
```
TEST iotest-qcow2: 229 [fail]
QEMU -- "/builddir/qemu-5.2.0/build/tests/qemu-iotests/../../qemu-system-x86_64" -nodefaults -display none -accel qtest
QEMU_IMG -- "/builddir/qemu-5.2.0/build/tests/qemu-iotests/../../qemu-img"
QEMU_IO -- "/builddir/qemu-5.2.0/build/tests/qemu-iotests/../../qemu-io" --cache writeback --aio threads -f qcow2
QEMU_NBD -- "/builddir/qemu-5.2.0/build/tests/qemu-iotests/../../qemu-nbd"
IMGFMT -- qcow2 (compat=1.1)
IMGPROTO -- file
PLATFORM -- Linux/x86_64 5.9.16_1
TEST_DIR -- /builddir/qemu-5.2.0/build/tests/qemu-iotests/scratch
SOCK_DIR -- /tmp/tmp.gRja3PqgOn
SOCKET_SCM_HELPER -- /builddir/qemu-5.2.0/build/tests/qemu-iotests/socket_scm_helper
--- /builddir/qemu-5.2.0/tests/qemu-iotests/229.out 2020-12-08 17:59:44.000000000 +0100
+++ /builddir/qemu-5.2.0/build/tests/qemu-iotests/229.out.bad 2021-01-21 10:50:21.549119104 +0100
@@ -8,7 +8,14 @@
=== Starting drive-mirror, causing error & stop ===
-{'execute': 'drive-mirror', 'arguments': {'device': 'testdisk', 'format': 'IMGFMT', 'target': 'blkdebug:TEST_DIR/blkdebug.conf:TEST_DIR/d.IMGFMT', 'sync': 'full', 'mode': 'existing', 'on-source-error': 'stop', 'on-target-error': 'stop' }}
+{'execute': 'drive-mirror',
+ 'arguments': {'device': 'testdisk',
+ 'format': 'IMGFMT',
+ 'target': 'blkdebug:TEST_DIR/blkdebug.conf:TEST_DIR/d.IMGFMT',
+ 'sync': 'full',
+ 'mode': 'existing',
+ 'on-source-error': 'stop',
+ 'on-target-error': 'stop' }}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "testdisk"}}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "testdisk"}}
{"return": {}}
@@ -17,7 +24,9 @@
=== Force cancel job paused in error state ===
-{'execute': 'block-job-cancel', 'arguments': { 'device': 'testdisk', 'force': true}}
+{'execute': 'block-job-cancel',
+ 'arguments': { 'device': 'testdisk',
+ 'force': true}}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "testdisk"}}
{"return": {}}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "aborting", "id": "testdisk"}}
TEST iotest-qcow2: 244
TEST iotest-qcow2: 249 [fail]
QEMU -- "/builddir/qemu-5.2.0/build/tests/qemu-iotests/../../qemu-system-x86_64" -nodefaults -display none -accel qtest
QEMU_IMG -- "/builddir/qemu-5.2.0/build/tests/qemu-iotests/../../qemu-img"
QEMU_IO -- "/builddir/qemu-5.2.0/build/tests/qemu-iotests/../../qemu-io" --cache writeback --aio threads -f qcow2
QEMU_NBD -- "/builddir/qemu-5.2.0/build/tests/qemu-iotests/../../qemu-nbd"
IMGFMT -- qcow2 (compat=1.1)
IMGPROTO -- file
PLATFORM -- Linux/x86_64 5.9.16_1
TEST_DIR -- /builddir/qemu-5.2.0/build/tests/qemu-iotests/scratch
SOCK_DIR -- /tmp/tmp.gRja3PqgOn
SOCKET_SCM_HELPER -- /builddir/qemu-5.2.0/build/tests/qemu-iotests/socket_scm_helper
--- /builddir/qemu-5.2.0/tests/qemu-iotests/249.out 2020-12-08 17:59:44.000000000 +0100
+++ /builddir/qemu-5.2.0/build/tests/qemu-iotests/249.out.bad 2021-01-21 10:50:22.114119114 +0100
@@ -7,24 +7,29 @@
=== Send a write command to a drive opened in read-only mode (1)
-{ 'execute': 'human-monitor-command', 'arguments': {'command-line': 'qemu-io none0 "aio_write 0 2k"'}}
+{ 'execute': 'human-monitor-command',
+ 'arguments': {'command-line': 'qemu-io none0 "aio_write 0 2k"'}}
{"return": "Block node is read-onlyrn"}
=== Run block-commit on base using an invalid filter node name
-{ 'execute': 'block-commit', 'arguments': {'job-id': 'job0', 'device': 'none1', 'top-node': 'int', 'filter-node-name': '1234'}}
+{ 'execute': 'block-commit',
+ 'arguments': {'job-id': 'job0', 'device': 'none1', 'top-node': 'int',
+ 'filter-node-name': '1234'}}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "job0"}}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "null", "id": "job0"}}
{"error": {"class": "GenericError", "desc": "Invalid node name"}}
=== Send a write command to a drive opened in read-only mode (2)
-{ 'execute': 'human-monitor-command', 'arguments': {'command-line': 'qemu-io none0 "aio_write 0 2k"'}}
+{ 'execute': 'human-monitor-command',
+ 'arguments': {'command-line': 'qemu-io none0 "aio_write 0 2k"'}}
{"return": "Block node is read-onlyrn"}
=== Run block-commit on base using the default filter node name
-{ 'execute': 'block-commit', 'arguments': {'job-id': 'job0', 'device': 'none1', 'top-node': 'int'}}
+{ 'execute': 'block-commit',
+ 'arguments': {'job-id': 'job0', 'device': 'none1', 'top-node': 'int'}}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "created", "id": "job0"}}
{"timestamp": {"seconds": TIMESTAMP, "microseconds": TIMESTAMP}, "event": "JOB_STATUS_CHANGE", "data": {"status": "running", "id": "job0"}}
{"return": {}}
@@ -36,6 +41,7 @@
=== Send a write command to a drive opened in read-only mode (3)
-{ 'execute': 'human-monitor-command', 'arguments': {'command-line': 'qemu-io none0 "aio_write 0 2k"'}}
+{ 'execute': 'human-monitor-command',
+ 'arguments': {'command-line': 'qemu-io none0 "aio_write 0 2k"'}}
{"return": "Block node is read-onlyrn"}
*** done
TEST iotest-qcow2: 251
TEST iotest-qcow2: 252
TEST iotest-qcow2: 256
TEST iotest-qcow2: 259 [not run]
TEST iotest-qcow2: 265
TEST iotest-qcow2: 267
TEST iotest-qcow2: 268
TEST iotest-qcow2: 271
TEST iotest-qcow2: 283
TEST iotest-qcow2: 287
TEST iotest-qcow2: 290
TEST iotest-qcow2: 292
TEST iotest-qcow2: 299
TEST iotest-qcow2: 309
Not run: 259
Failures: 117 127 140 141 143 156 161 191 229 249
Failed 10 of 122 iotests
make[1]: *** [/builddir/qemu-5.2.0/tests/Makefile.include:144: check-block] Error 1
make[1]: Leaving directory '/builddir/qemu-5.2.0/build'
make: *** [GNUmakefile:11: check] Error 2
=> ERROR: qemu-5.2.0_1: do_check: '${make_cmd} ${make_check_args} ${make_check_target}' exited with 2
=> ERROR: in do_check() at common/build-style/configure.sh:32
```
Maybe depends on my hardware, I'm using a ryzen 7 or maybe it's better to wait that the c/c++ upgrade is finished.
next prev parent reply other threads:[~2021-01-21 21:02 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 10:40 [ISSUE] " gspe
2021-01-19 21:22 ` ericonr
2021-01-19 22:51 ` gspe
2021-01-19 22:55 ` ericonr
2021-01-20 17:55 ` gspe
2021-01-20 17:55 ` gspe
2021-01-21 1:41 ` ericonr
2021-01-21 1:42 ` ericonr
2021-01-21 21:02 ` gspe [this message]
2021-01-21 21:10 ` ericonr
2021-01-21 21:15 ` gspe
2021-01-21 21:19 ` ericonr
2021-01-21 21:21 ` gspe
2021-01-21 21:22 ` gspe
2021-01-21 21:23 ` gspe
2021-01-21 21:24 ` gspe
2021-01-21 21:28 ` ericonr
2021-01-24 15:14 ` ackalker
2021-01-24 15:17 ` ackalker
2021-01-24 15:19 ` ackalker
2021-01-24 15:21 ` ackalker
2021-01-24 15:28 ` ackalker
2021-01-24 15:42 ` ackalker
2021-01-24 15:46 ` ackalker
2021-01-24 15:48 ` ackalker
2021-01-24 17:39 ` ackalker
2021-01-24 17:39 ` ackalker
2021-01-24 17:45 ` ackalker
2021-01-24 17:46 ` ackalker
2021-01-24 17:47 ` ackalker
2021-01-24 17:48 ` ackalker
2021-01-24 17:51 ` ackalker
2021-01-24 17:52 ` ackalker
2021-01-24 17:52 ` ackalker
2021-01-24 17:53 ` ackalker
2021-01-24 17:54 ` ackalker
2021-01-24 17:56 ` ackalker
2021-01-24 17:56 ` ackalker
2021-01-24 17:58 ` ackalker
2021-01-24 18:01 ` ackalker
2021-01-24 18:02 ` ackalker
2021-01-24 18:10 ` ackalker
2021-01-25 2:21 ` ackalker
2021-01-25 2:23 ` ackalker
2021-01-25 2:23 ` ackalker
2021-01-25 2:40 ` ackalker
2021-01-25 2:43 ` ackalker
2021-01-25 2:45 ` ackalker
2021-01-25 2:49 ` ackalker
2021-01-25 2:51 ` ackalker
2021-01-25 2:52 ` ackalker
2021-01-25 2:55 ` ackalker
2021-01-25 2:59 ` ackalker
2021-01-25 3:02 ` ackalker
2021-01-25 3:04 ` ackalker
2021-01-25 3:04 ` ackalker
2021-01-25 3:05 ` ackalker
2021-01-25 3:07 ` ackalker
2021-01-25 3:07 ` ackalker
2021-01-25 3:10 ` ackalker
2021-01-25 7:04 ` ackalker
2021-01-25 7:08 ` ackalker
2021-01-25 7:09 ` ackalker
2021-01-25 7:10 ` ackalker
2021-01-26 2:57 ` ackalker
2021-01-26 2:57 ` ackalker
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=20210121210224.0Miu-GNxUgzR5CPbpi-UzTW8oUfgp0FYXrjjhhUVwGY@z \
--to=gspe@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).