Bug 111696

Summary: [CI][DRMTIP] igt@kms_chamelium@hdmi-audio - fail - Failed assertion: success
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: not set    
Priority: not set CC: intel-gfx-bugs
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: SKL i915 features: display/Other

Description Lakshmi 2019-09-16 11:46:51 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-skl-6700k2/igt@kms_chamelium@hdmi-audio.html

	
Starting subtest: hdmi-audio
(kms_chamelium:1162) CRITICAL: Test assertion failure function test_display_audio, file ../tests/kms_chamelium.c:1946:
(kms_chamelium:1162) CRITICAL: Failed assertion: success
(kms_chamelium:1162) CRITICAL: Last errno: 2, No such file or directory
Subtest hdmi-audio failed.
Comment 1 CI Bug Log 2019-09-16 11:47:28 UTC 
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL:  igt@kms_chamelium@hdmi-audio - fail - Failed assertion: success
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-skl-6700k2/igt@kms_chamelium@hdmi-audio.html
Comment 2 Arek Hiler 2019-11-07 14:03:32 UTC 
There is so much things logged using igt_debug() that we overflow the ring buffer and we don't see which test has failed. 

e.g.

(kms_chamelium:1624) DEBUG: Audio flatline test result for format S16_LE, sampling rate 48000 Hz and 2 channels: ALL GREEN

if it has "FAILED" then we should promote it to igt_warn()
Comment 4 Martin Peres 2019-11-29 19:28:43 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/422.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.