jtreg
jtreg copied to clipboard
7903443: Propagate verbose flag to agents
work in progress...
Progress
- [ ] Change must be properly reviewed (1 review required, with at least 1 Reviewer)
- [x] Change must not contain extraneous whitespace
- [x] Commit message must refer to an issue
Issue
- CODETOOLS-7903443: Propagate verbose flag to agents (Bug - P3)
Reviewing
Using git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jtreg.git pull/187/head:pull/187
$ git checkout pull/187
Update a local copy of the PR:
$ git checkout pull/187
$ git pull https://git.openjdk.org/jtreg.git pull/187/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 187
View PR using the GUI difftool:
$ git pr show -t 187
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jtreg/pull/187.diff
:wave: Welcome back cstein! A progress list of the required criteria for merging this PR into master
will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.
@sormuras 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:
7903443: Propagate verbose flag to agents
Reviewed-by: jjg
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 4 new commits pushed to the master
branch:
- 779d1b223cfea1d79f93aa3db05161d444606c23: 7903736: Update GitHub actions used in jtreg's workflows
- 046a70d9cb582fe51245dd8ed3cb1baf797cd78c: 7903732: Verify that the java executable exists
- a66a5269e3c5eb6d8c612be811f9b0bad8bc73d5: 7903721: Update version to 7.5
- c40e6ea6d47dcdabba8715a6f70c55d89bdce693: 7903719: Release jtreg 7.4
Please see this link for an up-to-date comparison between the source branch of this pull request and the master
branch.
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 master
branch, type /integrate in a new comment.
@sormuras This pull request has been inactive for more than 8 weeks and will be automatically closed if another 8 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!
/integrate
Going to push as commit d890abfb880dcd4cb9b2fa2e09a7a058f5237044.
Since your change was applied there have been 4 commits pushed to the master
branch:
- 779d1b223cfea1d79f93aa3db05161d444606c23: 7903736: Update GitHub actions used in jtreg's workflows
- 046a70d9cb582fe51245dd8ed3cb1baf797cd78c: 7903732: Verify that the java executable exists
- a66a5269e3c5eb6d8c612be811f9b0bad8bc73d5: 7903721: Update version to 7.5
- c40e6ea6d47dcdabba8715a6f70c55d89bdce693: 7903719: Release jtreg 7.4
Your commit was automatically rebased without conflicts.
@sormuras Pushed as commit d890abfb880dcd4cb9b2fa2e09a7a058f5237044.
:bulb: You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.