diff options
| author | Gabriel Krisman Bertazi <krisman@collabora.co.uk> | 2017-10-30 15:54:53 -0200 |
|---|---|---|
| committer | Paulo Zanoni <paulo.r.zanoni@intel.com> | 2017-11-06 17:34:13 -0200 |
| commit | 9fe5a9a3de9e2ce345d5967a1e10a9a586b19836 (patch) | |
| tree | 7d63ffa712e0b090a00c39bb9fe8c50eecf411c8 /tests/kms_plane.c | |
| parent | bde7d72f58df18f86127b5b7fdcb89b64ee1a1d2 (diff) | |
tests/kms_fbcon_fbt: Report fbc_status on error
knowing the assertion triggered on wait_until_enabled() is not that
useful without knowing what exactly caused the failure. It might be an
user error, like too little stolen memory by the bios, or an actual
issue in the kernel. So, let's make life easier, particularly for the
CI, by printing the status before failing out.
Case in point:
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=101718
v2: Small typo.
Signed-off-by: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Diffstat (limited to 'tests/kms_plane.c')
0 files changed, 0 insertions, 0 deletions