Skip to content
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

8326725: [TESTBUG] [8u] Add keywords headful in MoveToOtherScreenTest.java test #460

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

yaqsun
Copy link
Contributor

@yaqsun yaqsun commented Feb 27, 2024

JDK-8164119 remove key attribute headful,
MoveToOtherScreenTest fails due wrong key attribute:
@key headful
isn't included in TEST.ROOT in jdk8.
But define "headful" jtreg keyword on JDK-8129822.
So add keywords headful in MoveToOtherScreenTest.java test.


Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8326725 needs maintainer approval

Issue

  • JDK-8326725: [TESTBUG] [8u] Add keywords headful in MoveToOtherScreenTest.java test (Bug - P4 - Requested)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/460/head:pull/460
$ git checkout pull/460

Update a local copy of the PR:
$ git checkout pull/460
$ git pull https://git.openjdk.org/jdk8u-dev.git pull/460/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 460

View PR using the GUI difftool:
$ git pr show -t 460

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/460.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Feb 27, 2024

👋 Welcome back yaqsun! 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.

@yaqsun
Copy link
Contributor Author

yaqsun commented Feb 27, 2024

/backport jdk8u-dev

@openjdk
Copy link

openjdk bot commented Feb 27, 2024

@yaqsun To use the /backport command, you need to be in the OpenJDK census and your GitHub account needs to be linked with your OpenJDK username (how to associate your GitHub account with your OpenJDK username).

@yaqsun yaqsun changed the title MoveToOtherScreenTest fails due wrong key attribute 8164119: MoveToOtherScreenTest fails due wrong key attribute Feb 27, 2024
@openjdk openjdk bot added the rfr Pull request is ready for review label Feb 27, 2024
@mlbridge
Copy link

mlbridge bot commented Feb 27, 2024

Webrevs

@theaoqi
Copy link
Member

theaoqi commented Feb 27, 2024

I think this should not be a backport of JDK-8164119. Maybe you should file a new JBS ID for this issue.

@yaqsun yaqsun changed the title 8164119: MoveToOtherScreenTest fails due wrong key attribute 8326725: [TESTBUG] [8u] Add keywords headful in MoveToOtherScreenTest.java test Feb 27, 2024
@yaqsun
Copy link
Contributor Author

yaqsun commented Feb 27, 2024

/approval 8326725 cancel

@openjdk
Copy link

openjdk bot commented Feb 27, 2024

@yaqsun
8326725: The approval request has been cancelled successfully.

@openjdk
Copy link

openjdk bot commented Feb 28, 2024

⚠️ @yaqsun This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

@yaqsun
Copy link
Contributor Author

yaqsun commented Feb 28, 2024

/approval 8164119 cancel

@openjdk
Copy link

openjdk bot commented Feb 28, 2024

@yaqsun This issue is not associated with this pull request.

Copy link
Member

@mrserb mrserb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should not be a backport of JDK-8164119. Maybe you should file a new JBS ID for this issue.

You are right.

@openjdk
Copy link

openjdk bot commented Mar 13, 2024

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 11, 2024

@yaqsun 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!

@bridgekeeper
Copy link

bridgekeeper bot commented May 9, 2024

@yaqsun This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.

@bridgekeeper bridgekeeper bot closed this May 9, 2024
@yaqsun
Copy link
Contributor Author

yaqsun commented May 14, 2024

/open

@openjdk openjdk bot reopened this May 14, 2024
@openjdk
Copy link

openjdk bot commented May 14, 2024

@yaqsun This pull request is now open

@yaqsun
Copy link
Contributor Author

yaqsun commented May 17, 2024

❗ This change is not yet ready to be integrated. See the Progress checklist in the description for automated requirements.

The Progress checklist in the description for automated requirements where can I see it from?

thanks.

@mrserb
Copy link
Member

mrserb commented Jun 11, 2024

❗ This change is not yet ready to be integrated. See the Progress checklist in the description for automated requirements.

The Progress checklist in the description for automated requirements where can I see it from?

thanks.

In the description of this PR:

Progress

Change must be properly reviewed (1 review required, with at least 1 Reviewer)
Change must not contain extraneous whitespace
Commit message must refer to an issue
JDK-8326725 needs maintainer approval

right now this PR does not have the "maintainer approval"

@yaqsun
Copy link
Contributor Author

yaqsun commented Jun 11, 2024

/approval 8326725 request

@openjdk
Copy link

openjdk bot commented Jun 11, 2024

@yaqsun
8326725: The approval request has been created successfully.

@yaqsun
Copy link
Contributor Author

yaqsun commented Jun 11, 2024

right now this PR does not have the "maintainer approval"

Thank you very much for your answer.

@openjdk openjdk bot added the approval label Jun 11, 2024
@mrserb
Copy link
Member

mrserb commented Jun 12, 2024

approval 8326725 request

You should provide the reason for the request and additional details, the list of requirements:
https://openjdk.org/projects/jdk-updates/approval.html

@yaqsun
Copy link
Contributor Author

yaqsun commented Jun 13, 2024

/approval 8326725 request Define "headful" jtreg keyword on JDK-8129822, so mark MoveToOtherScreenTest.java as @headful. Only this case is affected and the risk is low.

@openjdk
Copy link

openjdk bot commented Jun 13, 2024

@yaqsun
8326725: The approval request has been updated successfully.

@bridgekeeper
Copy link

bridgekeeper bot commented Jul 24, 2024

@yaqsun 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!

@mrserb
Copy link
Member

mrserb commented Aug 12, 2024

keep open

@bridgekeeper
Copy link

bridgekeeper bot commented Sep 9, 2024

@yaqsun 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!

@mrserb
Copy link
Member

mrserb commented Sep 10, 2024

keep open

@bridgekeeper
Copy link

bridgekeeper bot commented Oct 8, 2024

@yaqsun 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!

@mrserb
Copy link
Member

mrserb commented Oct 16, 2024

keep open

@bridgekeeper
Copy link

bridgekeeper bot commented Nov 14, 2024

@yaqsun 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!

@yaqsun
Copy link
Contributor Author

yaqsun commented Nov 14, 2024

please take a look

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 12, 2024

@yaqsun 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!

@yaqsun
Copy link
Contributor Author

yaqsun commented Dec 12, 2024

keep open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approval rfr Pull request is ready for review
Development

Successfully merging this pull request may close these issues.

3 participants