From 7d88885b72f4f632b289d472c2bcd659452eb478 Mon Sep 17 00:00:00 2001 From: Michelle McDaniel Date: Wed, 16 Nov 2016 16:04:40 -0800 Subject: [PATCH] Remove test exclusions for tests that now pass This change removes tests that have been fixed for x86 RyuJIT. It also updates the Issues for the remaining tests with additional details. --- tests/issues.targets | 35 +++++++---------------------------- 1 file changed, 7 insertions(+), 28 deletions(-) diff --git a/tests/issues.targets b/tests/issues.targets index 7026c26..4b19653 100644 --- a/tests/issues.targets +++ b/tests/issues.targets @@ -190,52 +190,31 @@ - 3392 + 3392, test is useful to have because it can be run manually when making changes to the GC that can have effects in OOM scenarios, but not appropriate to run on our current test infrastructure. - 3392 + 3392, test is useful to have because it can be run manually when making changes to the GC that can have effects in OOM scenarios, but not appropriate to run on our current test infrastructure. - 3392 + 3392, test is useful to have because it can be run manually when making changes to the GC that can have effects in OOM scenarios, but not appropriate to run on our current test infrastructure. - 3392 - - - 2413 - - - 2413 - - - 2412 - - - 2412 + 3392, test is useful to have because it can be run manually when making changes to the GC that can have effects in OOM scenarios, but not appropriate to run on our current test infrastructure. tail. call pop ret is only supported on amd64 - needs triage + needs triage: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. - needs triage - - - needs triage + needs triage: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. 2420. x86 JIT doesn't support implicit tail call optimization or tail. call pop ret sequence - - 7038,7173 - - 7163 - - - needs triage + 7163, fails on both legacy backend and RyuJIT The test is too large for x86 and causes OutOfMemory exception. -- 2.7.4