Bug 1249500
Summary: | 3 upstream tests failed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Tomas Pelka <tpelka> |
Component: | gstreamer1-plugins-bad-free | Assignee: | Wim Taymans <wtaymans> |
Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | wtaymans |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-12-15 07:35:46 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tomas Pelka
2015-08-03 08:08:01 UTC
For ppcl4 only elements/camerabin failed - http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2015/07/10343/1034320/2118751/32903946/TESTOUT.log (In reply to Tomas Pelka from comment #0) > Description of problem: > 3 upstream tests failed > FAIL: libs/aggregator > FAIL: elements/camerabin > FAIL: elements/audiomixer > The same result on x86_64 - http://lab-02.rhts.eng.bos.redhat.com/beaker/logs/tasks/32983+/32983868/TESTOUT.log s390x results -> 3 fail again FAIL: libs/gstglmemory FAIL: elements/camerabin FAIL: elements/audiomixer Can I log onto a machine to debug? camerabin is an expected failure (it's in the bad module after all) make elements/audiomixer.check seems to work reliably, don't know yet why it fails when run as make check. gstglmemory needs an X server to work. I'm now trying to run the same tests on a rhel-7.2 VM with nightly build. audiomixer and glmemory checks work fine in a VM with latest 7.3 snapshot. camerabin still fails (but in the same way as upstream). After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |