-
Notifications
You must be signed in to change notification settings - Fork 145
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
Bump weld from 6.0.0.Beta4 to 6.0.0.CR1 #25218
base: 8.0
Are you sure you want to change the base?
Conversation
Thank you so much! :) |
CR1 needs IP Team assistance still (https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/17290). |
#1 Failed with
|
Next run fails with the same test. |
And nothing in server.log. I can run it with full logging if you need ...? |
Ooo, yes, that would be great! The stack trace currently present in server.log seems to be not related to 500 reported. I have not inspected scripts how to run those tests locally. But if this is a case of series of some commands - I'd be happy to learn how to do it myself. |
Delete all logger settings and leave just these set to FINEST:
Then I open another shell and run tail (Kubuntu's Konsole is very good in searching):
Then I executed this (you can try to eliminate other tests in build.xml too if you need to repeat it thousand times)
|
Seems there is some breaking change in Weld - here are some stacktraces this test generates in server.log. Basically it cannot load some generated class:
|
weld/core@6.0.0.Beta4...6.0.0.CR1
weld/api@6.0.Beta4...6.0.CR1
The issue reported for Beta1 (https://gitlab.eclipse.org/eclipsefdn/emo-team/iplab/-/issues/15605) is claimed to be resolved in CR1.