| Summary: | media-plugins/gst-plugins-cdparanoia fails tests | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Gilles Dartiguelongue (RETIRED) <eva> |
| Component: | New packages | Assignee: | GStreamer package maintainers <gstreamer> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | gnome, pacho |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Gilles Dartiguelongue (RETIRED)
2008-12-30 10:46:00 UTC
Created attachment 176856 [details]
build.log
here is the build.log
as you can see, it fails with errors along the line of "no gconfd/orbit server started for this session, stale nfs locks or no tcp/ip support ?" which is kind of expected in a sandbox. So I wondered what we should do about this and then it hit me that it's not checking cdparanoia at all, but all the gst-plugins-base plugins.
Ah silly me, it looks like it's just a duplicate of bug #244954 Running suite(s): subparse 93%: Checks: 15, Failures: 1, Errors: 0 elements/subparse.c:241:F:general:test_sami:0: 'g_list_length (buffers)' (1) is not equal to 'num' (2) the comment about running all the tests for building just one plugin still stands though. (In reply to comment #2) > the comment about running all the tests for building just one plugin still > stands though. The simple solution here is to not split the package (and instead use flags and use-deps), even though I know Mart doesn't like that method. The tests in all the separated plugin packages will always fail, I guess we should add RESTRICT=test to the eclasses. (arg not fixed) RESTRICT=testr has been added |