-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
8348029: Make gtest death tests work with real crash signals #23191
8348029: Make gtest death tests work with real crash signals #23191
Conversation
👋 Welcome back stuefe! A progress list of the required criteria for merging this PR into |
@tstuefe This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 19 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
25aed8f
to
8babf78
Compare
8babf78
to
93b880d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not a Reviewer but this looks good to me. Also very useful! Thanks @tstuefe.
Thanks @MBaesken and @SoniaZaldana /integrate |
Going to push as commit 48c7597.
Your commit was automatically rebased without conflicts. |
Small change adds a new macro to the gtest TEST macro zoo:
TEST_VM_CRASH_SIGNAL
. This one is a companion toTEST_VM_FATAL_ERROR_MSG
andTEST_VM_ASSERT_MSG
and allows to write gtest that test expected crashes to happen. I will need that for a regression test for https://bugs.openjdk.org/browse/JDK-8330174 , among other things.You use it like this:
Note that the string provided is platform dependent (signal names on Posix, SEH names on Windows).
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/23191/head:pull/23191
$ git checkout pull/23191
Update a local copy of the PR:
$ git checkout pull/23191
$ git pull https://git.openjdk.org/jdk.git pull/23191/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 23191
View PR using the GUI difftool:
$ git pr show -t 23191
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/23191.diff
Using Webrev
Link to Webrev Comment