Bug 106747 - [CI] igt@* - crash - An internal exception that should have been handled was not: UnicodeDecodeError
Summary: [CI] igt@* - crash - An internal exception that should have been handled was ...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: IGT (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard: ReadyForDev
Keywords:
: 107800 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-05-30 23:25 UTC by Martin Peres
Modified: 2019-02-14 16:19 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Martin Peres 2018-05-30 23:25:53 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_54/fi-cnl-psr/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-fullscreen.html

[  227.738733] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
[  227.801928] [drm:intel_dp_sink_crc [i915]] *ERROR* Panel is unable to calculate any CRC after 6 vblanks
Comment 1 Martin Peres 2018-05-30 23:26:36 UTC 
Moving to IGT.
Comment 2 Martin Peres 2018-06-19 22:33:14 UTC 
Cc:ing the IGT maintainers, hopefully they can check it out :)
Comment 3 Petri Latvala 2018-06-20 09:04:35 UTC 
The UnicodeDecodeError is in the results.json file as is, so it's produced at test run time, not an visualization generation error.

The test printed something that wasn't valid UTF-8, and piglit is assuming everything printed is text (a fair assumption, you can argue).

With the new runner this shouldn't be an issue any more. If this isn't reproduceable again, I don't know what else can be done to investigate this.
Comment 4 Petri Latvala 2018-09-03 12:32:03 UTC 
*** Bug 107800 has been marked as a duplicate of this bug. ***
Comment 5 Petri Latvala 2018-09-03 12:34:38 UTC 
Marking notourbug, we should be able to create a proper bug report of the test printing ickyness with igt_runner when that's deployed.
Comment 6 Lakshmi 2018-10-16 08:52:16 UTC 
Closing this bug, as we were unable to reproduce this bug.
Comment 7 Martin Peres 2018-10-16 08:58:16 UTC 
(In reply to Lakshmi from comment #6)
> Closing this bug, as we were unable to reproduce this bug.

Yes, the new runner made this issue impossible.
Comment 8 CI Bug Log 2019-02-14 16:19:32 UTC 
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.

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.