Skip to content

Conversation

@andrlos
Copy link
Contributor

@andrlos andrlos commented Dec 5, 2025

TestHeadless components was re-done to reflect issues raised in the #6653

@andrlos andrlos changed the title reenabling of testHeadlessComponents test [Issue 6653] reenabling of testHeadlessComponents test Dec 5, 2025
</disables>
<command>
export OJDK_VERSION_NUMBER=$(JDK_VERSION) JREJDK="jdk" TMPRESULTS=$(Q)$(REPORTDIR)$(D)report$(Q); \
$(JAVA_TO_TEST) -version; \
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I am on the fence about leaving this in for future debug purposes or just ditching it.

Copy link
Contributor

Choose a reason for hiding this comment

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

We print java information and all environment variables out at the start of each Jenkins job run, so I vote ditch to avoid duplication.

Copy link
Contributor

@karianna karianna left a comment

Choose a reason for hiding this comment

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

Code change looks good.

<comment>https://github.com/adoptium/aqa-tests/issues/5224</comment>
<impl>ibm</impl>
</disable>
<disable>
Copy link
Contributor

@sophia-guo sophia-guo Dec 9, 2025

Choose a reason for hiding this comment

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

Can we enable <impl>hotspot</impl> only before it's been verified by other vendor?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I mean.. sure, but.. can't we verify the changes in bulk with all the vendors and get a matrix of where it passes/fails? I either lack the priviledges or knowledge to do it myself, but it would seem like the most sensible way of doing it, since the test runs for approximately 10 minutes at most. But sure, hotspot only is a viable route to take..

Copy link
Contributor

@smlambert smlambert left a comment

Choose a reason for hiding this comment

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

From #6653 (comment)

I can continue testing manually individually but I believe there is probably a nicer way to test this and be thorough

Reviewers will run an AQA_Test_Pipeline as a final part of the review process, before bringing these changes in.

@jiekang
Copy link
Contributor

jiekang commented Dec 9, 2025

For reference, I believe the actual changes to TestHeadlessComponents to be accepted into AQA were done via: rh-openjdk/TestHeadlessComponents#13

@andrlos Were there any other changes that are relevant? This is helpful in case a reviewer wants to inspect those as well.

@andrlos
Copy link
Contributor Author

andrlos commented Dec 9, 2025

@jiekang you are right, that is the changeset.. no - there are no other relevant changes... and I thought, that I already linked it somewhere either here or in the issue, sorry
@smlambert anything expected from me for the time being regarding this at the moment?

@sophia-guo
Copy link
Contributor

@andrlos Could you take a look at the new comments added?

@andrlos
Copy link
Contributor Author

andrlos commented Dec 9, 2025

@sophia-guo you mean the one about the hotspot? I thought.. nevermind, will write it as a reply to the comment :-)

@karianna karianna requested a review from sophia-guo December 10, 2025 02:44
@andrlos
Copy link
Contributor Author

andrlos commented Dec 10, 2025

@sophia-guo , I disabled ibm and openj9

@sophia-guo
Copy link
Contributor

@sophia-guo sophia-guo merged commit 64107ea into adoptium:master Dec 11, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants