Summary: | sys-libs/libseccomp-2.3.3 fails test: FAIL: regression | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alexey+gentoo, alonbl |
Priority: | Normal | Keywords: | TESTFAILURE |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tbz2 logs.tbz2 sys-libs:libseccomp-2.3.3:20180112-032640.log temp.tbz2 tests.tbz2 vgcore files |
Description
Toralf Förster
2018-01-12 17:57:03 UTC
Created attachment 514494 [details]
emerge-info.txt
Created attachment 514496 [details]
emerge-history.txt
Created attachment 514498 [details]
environment
Created attachment 514500 [details]
etc.portage.tbz2
Created attachment 514502 [details]
logs.tbz2
Created attachment 514504 [details]
sys-libs:libseccomp-2.3.3:20180112-032640.log
Created attachment 514506 [details]
temp.tbz2
Created attachment 514508 [details]
tests.tbz2
Also reproduced with sys-libs/libseccomp-2.3.2, sys-kernel/gentoo-sources-4.9.95 Just tested with the latest versions of libseccomp and valgrind, this still happens. All valgrind tests fail with return code 132. Bug 511552 and 580470 are duplicates of this (could we rename the bug to include valgrind? all other tests pass) The tests leave behind a vgcore file each, but I couldn't make anything out of them Created attachment 649164 [details]
vgcore files
Update summary. [something] is used when something refers to an overlay commit d7b7d0c23c6ed894ed37937833dcc50981a514af Author: Sam James <sam@gentoo.org> Date: Fri Nov 5 21:55:50 2021 +0000 sys-libs/libseccomp: add 2.5.3 Signed-off-by: Sam James <sam@gentoo.org> added libseccomp-2.5.3-skip-valgrind.patch |