stan/jdk-24
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

8271350: runtime/Safepoint tests use OutputAnalyzer::shouldMatch instead of shouldContaint

Browse Source 
Reviewed-by: mseledtsov, dholmes
This commit is contained in:
Igor Ignatyev 2021-07-27 23:20:19 +00:00
parent fbe28e4ee1
commit f1e15c8c8f
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/hotspot/jtreg/runtime/Safepoint/TestAbortOnVMOperationTimeout.java
View File

@ -74,7 +74,7 @@ public class TestAbortOnVMOperationTimeout {
if (shouldPass) {
output.shouldHaveExitValue(0);
} else {
output.shouldMatch("VM operation took too long");
output.shouldContain("VM operation took too long");
output.shouldNotHaveExitValue(0);
}
}

8
test/hotspot/jtreg/runtime/Safepoint/TestAbortVMOnSafepointTimeout.java
View File

@ -55,13 +55,13 @@ public class TestAbortVMOnSafepointTimeout {
);
OutputAnalyzer output = new OutputAnalyzer(pb.start());
output.shouldMatch("Timed out while spinning to reach a safepoint.");
output.shouldContain("Timed out while spinning to reach a safepoint.");
if (Platform.isWindows()) {
output.shouldMatch("Safepoint sync time longer than");
output.shouldContain("Safepoint sync time longer than");
} else {
output.shouldMatch("SIGILL");
output.shouldContain("SIGILL");
if (Platform.isLinux()) {
output.shouldMatch("(sent by kill)");
output.shouldContain("(sent by kill)");
}
}
output.shouldNotHaveExitValue(0);