-
Notifications
You must be signed in to change notification settings - Fork 83
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
7903872: Option testThreadFactoryPath support relativepath #233
Conversation
👋 Welcome back syan! A progress list of the required criteria for merging this PR into |
@sendaoYan 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 1 new commit pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@sormuras, @jaikiran) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
Webrevs
|
src/share/classes/com/sun/javatest/regtest/config/RegressionParameters.java
Outdated
Show resolved
Hide resolved
Do you know why the jtreg/src/share/classes/com/sun/javatest/regtest/config/RegressionParameters.java Lines 1243 to 1251 in cf42c7c
|
Thanks for the update to use NIO API. Please also extend the existing test in https://github.com/openjdk/jtreg/tree/master/test/testThreadFactory to use both kinds of paths: one absolute path and one relative path. |
TestThreadFactoryRelativePath has been added for test the relative path. The test has been verified locally.
|
GHA report failure |
@sendaoYan This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration! |
/open |
@sendaoYan This pull request is already open |
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.
Looks good to me.
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.
This looks good to me. I haven't had a chance to run the test myself. Please verify that this updated test as well as existing tests continue to pass, before integrating.
Thanks all for the review. The newly added tests and the existing tests run passed locally. /integrate |
@sendaoYan |
/sponsor |
@jaikiran @sendaoYan Pushed as commit 8e74d55. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Thanks for the sponsor. |
Hi all,
Currently, the jtreg option
-testThreadFactoryPath
doesn't support relativepath.I think jtreg can support relativepath for option
-testThreadFactoryPath
, same like to-jdk
or-nativepath
.Change has been verified locally, risk is low.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jtreg.git pull/233/head:pull/233
$ git checkout pull/233
Update a local copy of the PR:
$ git checkout pull/233
$ git pull https://git.openjdk.org/jtreg.git pull/233/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 233
View PR using the GUI difftool:
$ git pr show -t 233
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jtreg/pull/233.diff
Using Webrev
Link to Webrev Comment