0x1a/0x1e
<4>[ 414.327853] do_syscall_64+0x54/0x7e
<4>[ 414.327856] entry_SYSCALL_64_after_hwframe+0x44/0xa9
<4>[ 414.327859] RIP: 0033:0x7898a2f88f07
> -Original Message-
> From: Auld, Matthew
> Sent: Wednesday, June 16, 2021 5:29 AM
> To: intel-gfx@lists
Why are so many IGT tests blacklisted? How does a test get put on the
blacklist? We've been running the full (almost) IGT suite on Chrome OS. Our
blacklist has around 46 tests, mainly for tests that timeout, hang the system
and don't reboot, or cause a reboot in the middle of the test. I'm won
Abandoning this patch because the piglit patch on which it depends was not
accepted. I will submit a new patch that uses the approved piglit change.
From: Mason, Michael W
Sent: Monday, May 18, 2015 2:59 PM
To: intel-gfx@lists.freedesktop.org
Cc: Mason
We're running i-g-t on Chrome OS and seeing gem_tiled_fence_blits failures.
More specifically, the test is getting killed by the OOM killer, sometimes
leading to hangs and reboots. This happens consistently when the UI is
running. When the UI is stopped, the test passes. This makes sense sin
From: Mike Mason
gem_mmap seg faults when all tests are run together. This occurs because
the new-object subtest closes the gem object, but short-mmap assumes
it still exists. Thus gem_mmap__cpu() returns nil for addr and memset()
seg faults. This patch makes new-object and short-mmap create and
Piglit allows multiple -t and -x regular expressions to be
given on the command line. This patch enables run-tests.sh to
support that as well.
Signed-off-by: Mike Mason
---
scripts/run-tests.sh | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/scripts/run-tests.sh b/scrip
This patch just adds kms_flip_event_leak to tests/.gitignore.
Signed-off-by: Mike Mason
---
tests/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tests/.gitignore b/tests/.gitignore index d14d87b..3da061e 100644
--- a/tests/.gitignore
+++ b/tests/.gitignore
@@ -121,6 +121,7 @@ kms