8000 [quarkus-next] Aurora CI fails with missing quarkus-bom:999-SNAPSHOT … by Pepo48 · Pull Request #48595 · keycloak/keycloak · GitHub
[go: up one dir, main page]
Skip to content

[quarkus-next] Aurora CI fails with missing quarkus-bom:999-SNAPSHOT … - #48595

Merged
vmuzikar merged 1 commit into
keycloak:mainfrom
Pepo48:issue-48594
May 5, 2026
Merged

[quarkus-next] Aurora CI fails with missing quarkus-bom:999-SNAPSHOT …#48595
vmuzikar merged 1 commit into
keycloak:mainfrom
Pepo48:issue-48594

Conversation

@Pepo48
@Pepo48 Pepo48 commented Apr 29, 2026
Copy link
Copy Markdown
Contributor

…on remote EC2 VM

Closes: #48594

@Pepo48
[quarkus-next] Aurora CI fails with missing quarkus-bom:999-SNAPSHOT …
11b8748 
…on remote EC2 VM

Closes: keycloak#48594

Signed-off-by: Peter Zaoral <pzaoral@redhat.com>
@Pepo48
Pepo48 requested a review from a team as a code owner April 29, 2026 15:09
@Pepo48
Pepo48 requested review from ahus1 and pruivo April 29, 2026 15:10
@Pepo48
Pepo48 commented Apr 29, 2026
Copy link
Copy Markdown
Contributor Author

The idea is that the inventory-level setting is redundant here (the keycloak_remote_installer role already sets it for tasks that need root). Then Maven can run as ec2-user and finds local .m2 correctly.

@pruivo @ahus1 can you test this? It should be doable from your own fork (with Aurora credentials set up):

1. cherrypick this PR onto <your-fork>/main
2. git push origin --delete quarkus-next # to prevent conflicts on your fork, the branch will be recreated
3. gh workflow run quarkus-next.yml --repo <your-fork>/keycloak --ref main # to run the workflow, the same can be done via UI

@pruivo
pruivo commented Apr 29, 2026
Copy link
Copy Markdown
Member

@Pepo48 triggered: https://github.com/pruivo/keycloak/actions/runs/25118674050

This was referenced Apr 29, 2026
Closed
Closed
Closed
Closed
Closed
Closed
keycloak-github-bot[bot]
keycloak-github-bot Bot reviewed Apr 29, 2026
View reviewed changes
@keycloak-github-bot keycloak-github-bot Bot left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Unreported flaky test detected, please review

@keycloak-github-bot
keycloak-github-bot Bot commented Apr 29, 2026
Copy link
Copy Markdown

Unreported flaky test detected

If the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR.

org.keycloak.testsuite.model.user.UserModelTest#testAddDirtyRemoveFederationUsersInTheSameGroupConcurrent

Keycloak CI - Store Model Tests

java.lang.NullPointerException
	at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:483)
	at java.base/java.util.concurrent.ForkJoinTask.getException(ForkJoinTask.java:561)
...

Report flaky test

@pruivo
pruivo commented Apr 29, 2026
Copy link
Copy Markdown
Member

@Pepo48, it failed to compile. Is there a step missing?

@ahus1
ahus1 removed their request for review April 30, 2026 19:32
@Pepo48
Pepo48 commented May 4, 2026
Copy link
Copy Markdown
Contributor Author

@pruivo yes, your main doesn't contain the fixes that currently lives solely on upstream/quarkus-next. That's why it failed.

I should've probably mentioned it explicitly, sorry for that. So just for the record:

  1. Cherry-pick the this PR's commit onto /main
  2. Push upstream's quarkus-next to the fork (so prepare-quarkus-next.sh can cherry-pick fix commits from it):
git fetch upstream quarkus-next
git push origin upstream/quarkus-next:quarkus-next --force
  1. Trigger the workflow:
    gh workflow run quarkus-next.yml --repo <your-fork>/keycloak --ref main

Thanks for your time!

@pruivo
pruivo commented May 4, 2026
Copy link
Copy Markdown
Member

hmm, got [ERROR] Non-resolvable import POM: The following artifacts could not be resolved: io.quarkus:quarkus-bom:pom:999-SNAPSHOT (absent): Could not find artifact io.quarkus:quarkus-bom:pom:999-SNAPSHOT @ line 329, column 25 -> [Help 2]

https://github.com/pruivo/keycloak/actions/runs/25326817101/job/74272388542

@Pepo48
Pepo48 commented May 4, 2026 •
edited
Loading
Copy link
Copy Markdown
Contributor Author

@pruivo good, that means that quarkus-next branch is now where we wanted it to be.

Now the other error you got. My guess is that the main branch on your fork diverged in the meantime and it does not contain the fix from this PR (first step?). Because it's the very same error that this PR is suppose to fix.

@pruivo
pruivo commented May 4, 2026
Copy link
Copy Markdown
Member

Yeah, I think I forgot to push your commit to my main branch 😅 🤦
I think it works as it moved forward and started to execute the tests 🥳

https://github.com/pruivo/keycloak/actions/runs/25339715907/job/74294021335

@vmuzikar
vmuzikar commented May 5, 2026
Copy link
Copy Markdown
Contributor

@pruivo Please let me know when this looks good from your perspective and we can merge.

pruivo
pruivo approved these changes May 5, 2026
View reviewed changes
@pruivo pruivo left a comment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM @vmuzikar @Pepo48
Thank you.

vmuzikar
vmuzikar approved these changes May 5, 2026
View reviewed changes
@vmuzikar vmuzikar left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Approving based on @pruivo's review.

@vmuzikar
vmuzikar merged commit 18fec3e into keycloak:main May 5, 2026
88 checks passed
@stianst stianst mentioned this pull request Jun 1, 2026
Closed
sashyo pushed a commit to tide-foundation/keycloak-IGA that referenced this pull request Jul 20, 2026
@Pepo48 @sashyo
[quarkus-next] Aurora CI fails with missing quarkus-bom:999-SNAPSHOT …
cb751f1 
…on remote EC2 VM (keycloak#48595)

Closes: keycloak#48594

Signed-off-by: Peter Zaoral <pzaoral@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pruivo pruivo pruivo approved these changes
@vmuzikar vmuzikar vmuzikar approved these changes
+1 more reviewer
@keycloak-github-bot keycloak-github-bot[bot] keycloak-github-bot[bot] left review comments
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

flaky-test

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[quarkus-next] Aurora CI fails with missing quarkus-bom:999-SNAPSHOT on remote EC2 VM

3 participants

@Pepo48 @pruivo @vmuzikar
0