RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1249500 - 3 upstream tests failed
Summary: 3 upstream tests failed
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gstreamer1-plugins-bad-free
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Wim Taymans
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-03 08:08 UTC by Tomas Pelka
Modified: 2020-12-15 07:35 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:35:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Pelka 2015-08-03 08:08:01 UTC
Description of problem:
3 upstream tests failed
FAIL: libs/aggregator
FAIL: elements/camerabin
FAIL: elements/audiomixer

Version-Release number of selected component (if applicable):
gstreamer1-plugins-bad-free-1.4.5-2.el7

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:
3 tests failed

Expected results:


Additional info:
Full log at http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2015/07/10343/1034320/2118750/32903938/TESTOUT.log

Comment 1 Tomas Pelka 2015-08-03 08:08:41 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

Comment 2 Tomas Pelka 2015-08-03 09:41:46 UTC
(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

Comment 3 Tomas Pelka 2015-08-03 13:51:53 UTC
s390x results -> 3 fail again

FAIL: libs/gstglmemory
FAIL: elements/camerabin
FAIL: elements/audiomixer

Comment 4 Wim Taymans 2015-08-20 11:11:25 UTC
Can I log onto a machine to debug?

Comment 5 Wim Taymans 2015-09-07 16:02:15 UTC
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.

Comment 6 Wim Taymans 2016-03-29 13:59:22 UTC
audiomixer and glmemory checks work fine in a VM with latest 7.3 snapshot. 

camerabin still fails (but in the same way as upstream).

Comment 8 RHEL Program Management 2020-12-15 07:35:46 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.