From: "WANG Xuerui" <xen0n@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtbase/
Date: Sun, 24 Sep 2023 17:09:01 +0000 (UTC) [thread overview]
Message-ID: <1695575119.efa8fedcff3a8c52d5cc6091d7cdd4b7971c9898.xen0n@gentoo> (raw)
commit: efa8fedcff3a8c52d5cc6091d7cdd4b7971c9898
Author: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 24 15:48:01 2023 +0000
Commit: WANG Xuerui <xen0n <AT> gentoo <DOT> org>
CommitDate: Sun Sep 24 17:05:19 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=efa8fedc
dev-qt/qtbase: keyword 6.5.2-r2 for ~loong
Two test cases are failing on a Loongson 3A6000 box:
71 - tst_qprocess (Failed)
304 - tst_qnetworkinterface (Failed)
With the following log messages:
FAIL! : tst_QProcess::startStopStartStopBuffers(separate-separate) 'process.bytesToWrite() > 0' returned FALSE. ()
Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)]
FAIL! : tst_QProcess::startStopStartStopBuffers(separate-merged) 'process.bytesToWrite() > 0' returned FALSE. ()
Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)]
FAIL! : tst_QProcess::startStopStartStopBuffers(merged-separate) 'process.bytesToWrite() > 0' returned FALSE. ()
Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)]
FAIL! : tst_QProcess::startStopStartStopBuffers(merged-merged) 'process.bytesToWrite() > 0' returned FALSE. ()
Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)]
FAIL! : tst_QProcess::startStopStartStopBuffers(merged-forwarded) 'process.bytesToWrite() > 0' returned FALSE. ()
Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/corelib/io/qprocess/tst_qprocess.cpp(2461)]
FAIL! : tst_QNetworkInterface::localAddress(wg0-xxx.xxx.xxx.xxx) 'pmtu <= outgoingIface->maximumTransmissionUnit()' returned FALSE. ()
Loc: [/tmp/portage/dev-qt/qtbase-6.5.2-r2/work/qtbase-everywhere-src-6.5.2/tests/auto/network/kernel/qnetworkinterface/tst_qnetworkinterface.cpp(246)]
But both are spurious to some extent.
For the startStopStartStopBuffers case, a 128KiB write is made to
hopefully retain some unwritten data even if the pipe is found writable,
and the comment in the test code indicates that Linux is the "worst
case" defaulting to 64KiB pipe buffers. This is actually
PIPE_DEF_BUFFERS pages, according to include/linux/pipe_fs_i.h; popular
arches use 4KiB pages, so 64KiB for them. Linux/LoongArch defaults to
16KiB pages, however, and the test case passes when the write size is
quadrupled.
And for the localAddress case, it may just be that the WireGuard
interface behaves differently than physical ones, and indeed the other
interfaces passed the test.
So, the library should actually be fully functional on loong, hence the
keyword.
Signed-off-by: WANG Xuerui <xen0n <AT> gentoo.org>
dev-qt/qtbase/qtbase-6.5.2-r2.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-qt/qtbase/qtbase-6.5.2-r2.ebuild b/dev-qt/qtbase/qtbase-6.5.2-r2.ebuild
index 2f489c953187..67ce1f180005 100644
--- a/dev-qt/qtbase/qtbase-6.5.2-r2.ebuild
+++ b/dev-qt/qtbase/qtbase-6.5.2-r2.ebuild
@@ -8,7 +8,7 @@ inherit flag-o-matic qt6-build toolchain-funcs
DESCRIPTION="Cross-platform application development framework"
if [[ ${QT6_BUILD_TYPE} == release ]]; then
- KEYWORDS="amd64 ~arm ~arm64 ~hppa ~x86"
+ KEYWORDS="amd64 ~arm ~arm64 ~hppa ~loong ~x86"
fi
declare -A QT6_IUSE=(
next reply other threads:[~2023-09-24 17:09 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 17:09 WANG Xuerui [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-16 11:18 [gentoo-commits] repo/gentoo:master commit in: dev-qt/qtbase/ Arthur Zamarin
2025-04-15 10:22 Sam James
2025-04-09 22:05 Ionen Wolkens
2025-03-26 12:29 Ionen Wolkens
2025-02-26 8:47 Ionen Wolkens
2025-02-26 8:47 Ionen Wolkens
2025-02-26 8:47 Ionen Wolkens
2025-02-22 14:46 Arthur Zamarin
2025-02-20 22:38 James Le Cuirot
2025-02-02 12:27 Ionen Wolkens
2024-12-27 12:02 Sam James
2024-12-18 4:37 Ionen Wolkens
2024-12-18 4:37 Ionen Wolkens
2024-12-03 18:16 Ionen Wolkens
2024-11-02 14:10 Arthur Zamarin
2024-11-01 6:35 Arthur Zamarin
2024-10-09 6:22 Ionen Wolkens
2024-09-03 7:44 Ionen Wolkens
2024-09-02 17:52 Ionen Wolkens
2024-08-26 22:08 Ionen Wolkens
2024-08-25 20:27 Eli Schwartz
2024-07-25 6:22 Ionen Wolkens
2024-07-25 6:22 Ionen Wolkens
2024-07-25 6:22 Ionen Wolkens
2024-07-22 22:53 Ionen Wolkens
2024-07-21 12:54 Ionen Wolkens
2024-07-08 16:40 Arthur Zamarin
2024-07-08 10:09 Sam James
2024-07-03 0:39 Ionen Wolkens
2024-06-02 8:22 Ionen Wolkens
2024-04-02 6:09 Arthur Zamarin
2024-03-30 0:29 Ionen Wolkens
2024-03-25 22:10 Ionen Wolkens
2024-03-24 18:39 Ionen Wolkens
2024-03-22 6:16 Arthur Zamarin
2024-02-29 2:09 Ionen Wolkens
2024-01-23 14:36 Ionen Wolkens
2024-01-23 14:36 Ionen Wolkens
2024-01-19 22:13 Ionen Wolkens
2024-01-08 21:09 Ionen Wolkens
2024-01-08 12:59 Ionen Wolkens
2024-01-08 12:59 Ionen Wolkens
2024-01-07 15:20 Ionen Wolkens
2024-01-07 15:20 Ionen Wolkens
2023-12-18 1:37 Ionen Wolkens
2023-12-01 19:48 Jakov Smolić
2023-12-01 7:04 Ionen Wolkens
2023-12-01 6:21 Sam James
2023-12-01 6:21 Sam James
2023-11-30 5:29 Ionen Wolkens
2023-11-29 22:33 Sam James
2023-10-27 11:40 Ionen Wolkens
2023-10-27 11:40 Ionen Wolkens
2023-10-22 4:51 Ionen Wolkens
2023-10-17 21:19 Ionen Wolkens
2023-10-10 18:09 Ionen Wolkens
2023-10-10 14:51 Ionen Wolkens
2023-09-26 15:16 Ionen Wolkens
2023-09-26 12:24 Ionen Wolkens
2023-09-24 17:51 Ionen Wolkens
2023-09-24 17:09 WANG Xuerui
2023-09-22 20:53 Sam James
2023-09-20 8:32 Ionen Wolkens
2023-09-19 3:02 Ionen Wolkens
2023-09-19 3:02 Ionen Wolkens
2023-09-17 2:11 Ionen Wolkens
2023-09-17 1:59 Ionen Wolkens
2023-09-13 16:42 Ionen Wolkens
2023-09-13 16:42 Ionen Wolkens
2023-09-12 11:44 Ionen Wolkens
2023-09-12 11:44 Ionen Wolkens
2023-09-12 1:28 Sam James
2023-09-12 1:26 Sam James
2023-09-12 0:13 Ionen Wolkens
2023-09-11 22:59 Sam James
2023-09-09 16:22 Ionen Wolkens
2023-09-09 16:22 Ionen Wolkens
2023-09-09 16:22 Ionen Wolkens
2023-09-06 8:49 Ionen Wolkens
2023-09-05 14:31 Ionen Wolkens
2023-09-05 13:05 Ionen Wolkens
2023-06-10 14:33 Jimi Huotari
2023-06-10 14:33 Jimi Huotari
2023-06-02 15:39 Jimi Huotari
2023-05-24 6:52 Jimi Huotari
2023-05-23 2:52 Sam James
2023-05-06 11:26 Jimi Huotari
2023-04-17 19:39 Jimi Huotari
2023-04-17 19:39 Jimi Huotari
2023-03-26 16:59 Jimi Huotari
2023-03-19 13:09 Jimi Huotari
2023-02-09 10:02 Andreas Sturmlechner
2023-01-05 22:39 Jimi Huotari
2022-12-01 19:19 Andreas Sturmlechner
2022-09-24 14:32 Andreas Sturmlechner
2022-08-02 22:00 Sam James
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=1695575119.efa8fedcff3a8c52d5cc6091d7cdd4b7971c9898.xen0n@gentoo \
--to=xen0n@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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