Summary: | [CI] igt@* - crash - An internal exception that should have been handled was not: UnicodeDecodeError | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | IGT | Assignee: | Default DRI bug account <dri-devel> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | arkadiusz.hiler, intel-gfx-bugs, petri.latvala |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | i915 features: |
Description
Martin Peres
2018-05-30 23:25:53 UTC
Moving to IGT. Cc:ing the IGT maintainers, hopefully they can check it out :) 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. *** Bug 107800 has been marked as a duplicate of this bug. *** Marking notourbug, we should be able to create a proper bug report of the test printing ickyness with igt_runner when that's deployed. Closing this bug, as we were unable to reproduce this bug. (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. 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.