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

Run optimized dist whenever possible in Quarkus IT #29117

Closed
Tracked by #25931
vmuzikar opened this issue Apr 26, 2024 · 1 comment
Closed
Tracked by #25931

Run optimized dist whenever possible in Quarkus IT #29117

vmuzikar opened this issue Apr 26, 2024 · 1 comment
Labels
area/dist/quarkus area/testsuite Indicates an issue on the Testsuite area kind/enhancement Categorizes a PR related to an enhancement team/cloud-native team/continuous-testing

Comments

@vmuzikar
Copy link
Contributor

Description

Augmentation takes a significant time. We should use an optimized dist whenever possible in the tests. This generally concerns tests that don't use build time options.

Discussion

No response

Motivation

No response

Details

No response
@vmuzikar vmuzikar added area/testsuite Indicates an issue on the Testsuite area kind/enhancement Categorizes a PR related to an enhancement area/dist/quarkus labels Apr 26, 2024
@vmuzikar vmuzikar mentioned this issue Apr 26, 2024
Open
2 tasks
@vmuzikar
Copy link
Contributor Author

After discussing this further offline with @shawkins, we decided not reject this. Using optimized dist would not bring too much of a perf gain. The slowest running tests utilize build time options.

@vmuzikar vmuzikar closed this as not planned Won't fix, can't repro, duplicate, stale Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/dist/quarkus area/testsuite Indicates an issue on the Testsuite area kind/enhancement Categorizes a PR related to an enhancement team/cloud-native team/continuous-testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vmuzikar