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

[BUG] Gradle analysis taking too long to complete #662

Closed
1 task done
jmle opened this issue Jul 17, 2024 · 2 comments · Fixed by #663
Closed
1 task done

[BUG] Gradle analysis taking too long to complete #662

jmle opened this issue Jul 17, 2024 · 2 comments · Fixed by #663
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@jmle
Copy link
Contributor

jmle commented Jul 17, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

0.5-beta2

Priority

Critical

Current Behavior

Currently, the analysis of the tackle-testapp-public in its gradle form takes too long to complete. This might be related to this bug opened in the hub:

konveyor/tackle2-addon-analyzer#128

Expected Behavior

Gradle analysis shouldn't take too much longer than Maven analysis.

How Reproducible

Always (Default)

Steps To Reproduce

Analyze tackle-testapp-public on its main branch (Maven) and then on its gradle branch (Gradle). Compare the time it takes for both to run.

Environment

No response

Anything else?

No response
@jmle jmle added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 17, 2024
@jmle jmle mentioned this issue Jul 17, 2024
Merged
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Jul 17, 2024
@jmle jmle closed this as completed in #663 Jul 18, 2024
@jmle jmle closed this as completed in 389f5d8 Jul 18, 2024
@jmle jmle reopened this Jul 24, 2024
@jmle
Copy link
Contributor Author

jmle commented Aug 5, 2024

Can't reproduce anymore in the latest d/s

@jmle jmle closed this as completed Aug 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Planning
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

🐛 Prevent gradle logic from decompressing jars all the time jmle/analyzer-lsp
1 participant
@jmle