Summary: | dev-libs/glib-2.56.2: [test] ERROR: network-monitor-race (core dumped) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
dev-libs:glib-2.56.2:20180820-124920.log.xz
test-suite.log emerge-info.txt |
Description
Michał Górny
2018-08-20 13:43:47 UTC
Created attachment 544088 [details]
dev-libs:glib-2.56.2:20180820-124920.log.xz
Created attachment 544090 [details]
test-suite.log
Created attachment 544092 [details]
emerge-info.txt
So I've rerun it a lot, and I seem to be reliably reproducing this problem. It happens also with py3.6, MAKEOPTS=-j1, -O0 -ggdb, USE=debug, and without network-sandbox. Curious enough, network-monitor test itself passes. Do you have any other ideas or should I report it upstream? The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=549542cf21eb81eb75ce4f526f6a0da92b686c26 commit 549542cf21eb81eb75ce4f526f6a0da92b686c26 Author: Mart Raudsepp <leio@gentoo.org> AuthorDate: 2018-11-29 15:24:07 +0000 Commit: Mart Raudsepp <leio@gentoo.org> CommitDate: 2018-11-29 15:24:41 +0000 dev-libs/glib: fix potential issues in network-monitor-race test Closes: https://bugs.gentoo.org/664106 Signed-off-by: Mart Raudsepp <leio@gentoo.org> Package-Manager: Portage-2.3.52, Repoman-2.3.11 ...56.2-network-monitor-race-test-iterations.patch | 36 ++++++++++++++++++++++ dev-libs/glib/glib-2.56.2.ebuild | 3 ++ 2 files changed, 39 insertions(+) hrm, looks like it still has failures sometimes :( Still passes fine on my desktop, but still fails on the arm64 box; I guess the patch I applied makes it never fail on my desktop, while previously sometimes rarely it could have failed there too.. 2.60 moves to meson test harness, so lets consider this one as fixed (the patch I did apply to 2.56.x) or obsolete and re-report any test problems against 2.60 |