summaryrefslogtreecommitdiff
path: root/dev-qt/qtwebengine/qtwebengine-6.5.9999.ebuild
diff options
context:
space:
mode:
authorIonen Wolkens <ionen@gentoo.org>2023-09-01 03:02:03 -0400
committerIonen Wolkens <ionen@gentoo.org>2023-09-05 09:01:10 -0400
commit5c22252b6764bd7e6a608421d9291997d3cdc450 (patch)
treeb55c50379f4a84ab1e86e281d7369e0bd964fd06 /dev-qt/qtwebengine/qtwebengine-6.5.9999.ebuild
parentcaabe7e6b93ebe85f814fa8a7eb63c15d4ea82f3 (diff)
downloadgentoo-5c22252b6764bd7e6a608421d9291997d3cdc450.tar.gz
gentoo-5c22252b6764bd7e6a608421d9291997d3cdc450.tar.bz2
gentoo-5c22252b6764bd7e6a608421d9291997d3cdc450.zip
dev-qt/qtscxml: skip flaky test with pid-sandbox (qt6)
clang16+glibc-2.38 -> pass clang16-musl-1.2.4 -> pass clang16[hardened]+glibc-2.38 -> pass gcc13+glibc-2.38 -> pass gcc13[hardened]+glibc-2.38 -> pass gcc12[hardened]+musl-1.2.4 -> fail ??? And then, it passes if FEATURES=-pid-sandbox, so it's at least not broken. Must be hitting some obscure codepath to be stopped by sandbox (or perhaps that chroot ended up with something different that activates something) Have not gotten to the bottom of this, but failing only when using sandbox is all I need to consider skipping it. Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Diffstat (limited to 'dev-qt/qtwebengine/qtwebengine-6.5.9999.ebuild')
0 files changed, 0 insertions, 0 deletions