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] Analysis of Gradle applications takes too long then fails #128

Open
1 task done
abrugaro opened this issue Jun 17, 2024 · 2 comments
Open
1 task done

[BUG] Analysis of Gradle applications takes too long then fails #128

abrugaro opened this issue Jun 17, 2024 · 2 comments
Assignees
@jmle
Labels
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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v0.5.0

Comments

@abrugaro
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

latest

Priority

Undefined (Default)

Current Behavior

When analyzing the gradle-multi-project-example applicationthe, the analysis takes more than 15 minutes and then fails when starting the dependency analysis

Attached you'll find the analysis details and the pod logs just before it fails (I cannot see the exact error since the pod is deleted before I can capture it).

Pod Logs
Analysis details

Expected Behavior

The analysis should complete successfully

How Reproducible

Always (Default)

Steps To Reproduce

  1. Create an application using the gradle-multi-project-example repositoy
  2. Analyze it selecting source code only or source code + deps analysis

Environment

No response

Anything else?

I'm opening this issue in the hub repository because the same analysis works in Kantra
@abrugaro abrugaro 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 Jun 17, 2024
@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 Jun 17, 2024
@dymurray dymurray added this to the v0.5.0 milestone Jun 20, 2024
@abrugaro
Copy link
Author

Relates to: https://issues.redhat.com/browse/MTA-3148

This was referenced Jul 17, 2024
Closed
Merged
jmle referenced this issue in konveyor/analyzer-lsp Jul 18, 2024
@jmle
🐛 Prevent gradle logic from decompressing jars all the time (#663)
389f5d8 
The gradle analysis was uncompressing jars every time because of a lack
of a check for the existence of the already decompressed directory.

- Related to https://github.com/konveyor/tackle2-hub/issues/667
- Partly fixes #662

Signed-off-by: Juan Manuel Leflet Estrada <[email protected]>
@dymurray dymurray added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jul 18, 2024
@konveyor-ci-bot konveyor-ci-bot bot removed the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Jul 18, 2024
@jortel jortel transferred this issue from konveyor/tackle2-hub Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jmle jmle

Labels
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. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
Planning
Status: ✅ Done
Milestone
v0.5.0
Development

No branches or pull requests
3 participants
@jmle @dymurray @abrugaro