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.

Sign up for GitHub

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

Jump to bottom

Update Quarkus to version 3.2.0.Final #831

Merged
merged 1 commit into from
Jul 14, 2023
Merged

Update Quarkus to version 3.2.0.Final #831

merged 1 commit into from
Jul 14, 2023

Conversation

fedinskiy
Copy link
Contributor

Summary

The title says it all

Please check the relevant options

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Dependency update
  • Refactoring
  • Breaking change (fix or feature that would cause existing functionality to change)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • Example scenarios has been updated / added
  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@fedinskiy fedinskiy requested a review from michalvavrik July 12, 2023 07:25
@fedinskiy fedinskiy force-pushed the feature/quarkus_320 branch 2 times, most recently from 077d369 to 0ac1b39 Compare July 14, 2023 10:16
michalvavrik
michalvavrik reviewed Jul 14, 2023
View reviewed changes
examples/quarkus-helm/pom.xml Show resolved Hide resolved
.github/workflows/pr.yaml Outdated Show resolved Hide resolved
@fedinskiy fedinskiy force-pushed the feature/quarkus_320 branch 3 times, most recently from 0f1db75 to 5d9ca3b Compare July 14, 2023 12:35
@fedinskiy
Copy link
Contributor Author

run tests

@michalvavrik
Copy link
Member

@fedinskiy I glanced at OC results, looks related, WDYT? This is not a good release for OpenShift :-D

@fedinskiy
Copy link
Contributor Author

fedinskiy commented Jul 14, 2023 •
edited
Loading

@michalvavrik this is quite peculiar, since all failures has Connection was closed in common.

My bet is on quarkusio/quarkus#34276 which should be fixed in 3.2.1.Final

UPD: it is the same issue, we encountered in #817

@fedinskiy fedinskiy force-pushed the feature/quarkus_320 branch from 5d9ca3b to df48a0e Compare July 14, 2023 16:30
@fedinskiy fedinskiy force-pushed the feature/quarkus_320 branch from df48a0e to 2106e41 Compare July 14, 2023 16:35
@fedinskiy
Copy link
Contributor Author

run tests

@michalvavrik michalvavrik merged commit f88c241 into quarkus-qe:main Jul 14, 2023
@michalvavrik michalvavrik mentioned this pull request Jul 15, 2023
Merged
10 tasks
@gtroitsk gtroitsk mentioned this pull request Jul 17, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@michalvavrik michalvavrik michalvavrik approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@fedinskiy @michalvavrik