diff options
| author | Tvrtko Ursulin <tvrtko.ursulin@intel.com> | 2021-03-31 12:02:08 +0100 |
|---|---|---|
| committer | Tvrtko Ursulin <tvrtko.ursulin@intel.com> | 2021-04-01 12:24:41 +0100 |
| commit | c37c8443313a9de4d6a286f755702524e00bae1b (patch) | |
| tree | 56307c483e0a03b8f72f1af4704df074ab5e9dbc /tests/intel-ci | |
| parent | 21f472af73a347f1cac38c0e838c94a19c83248c (diff) | |
tests/i915/gem_watchdog: Exercise long rendering chains
Test to demonstrate a problem with the proposed default fence expiry
semantics where long rendering chain get silently broken.
If we had fence error propagation (no clear agreement whether to do it or
not) maybe userspace would see if, assuming fence status is looked at, but
overall potential rendering corruption is the story in any case.
Note that this is not a single long batch but just a long queue of work
which could be viewed as heavy system load as well (like virtualisation
or other types of resource sharing).
v2:
* Fix commit message.
* Blacklist the test which is expected to fail for now.
Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
Diffstat (limited to 'tests/intel-ci')
| -rw-r--r-- | tests/intel-ci/blacklist.txt | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/tests/intel-ci/blacklist.txt b/tests/intel-ci/blacklist.txt index e186a29a..33f92e37 100644 --- a/tests/intel-ci/blacklist.txt +++ b/tests/intel-ci/blacklist.txt @@ -54,6 +54,7 @@ igt@gem_sync@(?!.*basic).* igt@gem_tiled_swapping@(?!non-threaded).* igt@gem_userptr_blits@(major|minor|forked|mlocked|swapping).* igt@gem_wait@hang.* +igt@gem_watchdog@far-fence igt@sysfs_heartbeat_interval@(long|off) igt@sysfs_preempt_timeout@off igt@sysfs_timeslice_duration@off |