Testsuite failure does not fail the build
Bug #1657425 reported by
Robie Basak
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| libseccomp (Debian) |
Fix Released
|
Unknown
|
|||
| libseccomp (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Bug 1450642 states: "seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log."
Presumably this is a separate bug that needs to be fixed, at least in the development release? IMHO bundling a fix in any future SRU should be fine, too.
| Changed in libseccomp (Debian): | |
| status: | Unknown → New |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in libseccomp (Ubuntu): | |
| status: | New → Fix Released |
| Changed in libseccomp (Debian): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package libseccomp - 2.3.1-2.1ubuntu3
---------------
libseccomp (2.3.1-2.1ubuntu3) artful; urgency=medium
* debian/rules: Make test failures cause the build to fail (LP: #1657425)
-- Tyler Hicks <email address hidden> Fri, 06 Oct 2017 18:08:21 +0000