forked from eclipse-jdt/eclipse.jdt.core
-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Build/Analyze seems stuck on org.eclipse.jdt.core.tests.regression.XLargeTest #1008
Comments
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.core
that referenced
this issue
Dec 3, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for eclipse-jdtls#1008
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.core
that referenced
this issue
Dec 3, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for eclipse-jdtls#1008
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.core
that referenced
this issue
Dec 3, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for eclipse-jdtls#1008
mickaelistria
added a commit
that referenced
this issue
Dec 3, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for #1008
mickaelistria
added a commit
that referenced
this issue
Dec 5, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for #1008
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.core
that referenced
this issue
Dec 6, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for eclipse-jdtls#1008
mickaelistria
added a commit
to mickaelistria/eclipse.jdt.core
that referenced
this issue
Dec 13, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for eclipse-jdtls#1008
datho7561
pushed a commit
that referenced
this issue
Dec 13, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for #1008
mickaelistria
added a commit
that referenced
this issue
Dec 15, 2024
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for #1008
mickaelistria
added a commit
that referenced
this issue
Jan 6, 2025
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for #1008
mickaelistria
added a commit
that referenced
this issue
Jan 7, 2025
Keep track in the context of the files that have compile errors so we only use ProceedOnErrorTransTypes on those and ignore it for files without errors (as it can cause some other issues, eg with XLargeTests being very slow) Workaround for #1008
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When building the workspace, it seems stuck on
TaskEvent[ANALYZE,...,org.eclipse.jdt.core.tests.regression.XLargeTest]
. It's actually processing but taking a very long time.Some stacks:
The text was updated successfully, but these errors were encountered: