-
Notifications
You must be signed in to change notification settings - Fork 50
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
fix tests path #1346
fix tests path #1346
Conversation
@sbouchet I see. Let's see how it goes. Just to make it clear, I have copied from old jenkins setup where the number of tests comig from PR was 1. (the dummy one). Not sure if that was alright before ;) |
no it wasn't alright even in master ! |
@koentsje : what do you think ? it enables back the full tests suite with 3835 tests and only 10 fails :) |
@sbouchet i am trying to figure out why there are failures because on my machine everything is normal... is there an easy way to get the raw surefire output? |
The build also seems to end successfully according to the logs, so I am not sure where these failed tests come from? :-\ 2021-05-19T13:42:23.7764886Z [INFO] ------------------------------------------------------------------------ |
The GitHub Action replaces the old Jenkins PR jobs. it does not fails on Build ( using this commandline mvn clean verify -U -fae --settings build-ci/maven-settings.xml -DskipITests=true -Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true --no-transfer-progress ) so it produces the reports that are then parsed by another action ( Test report ) |
@sbouchet Yes I understand and I have looked at the output (and the build logs) that you direct me to but it would be interesting to see the surefire output (and in particular the stack trace) of the particular tests that fail. I have absolutely no clue as to why e.g. the IllegalArgumentExceptions are generated as on my box all seems normal... |
f1f19bb
to
7290566
Compare
tried locally with the same args and also get a successful result without errors. I then tend to suspect that the image used to run the build (ubuntu) make those tests to fails. |
Ok sure, I can always disable the offending tests for now and try to reproduce on a Ubuntu image (but it will have to wait) But if I understand correctly there is no way to get/export the complete stack traces of these failing tests? It is quite tedious to have to search the raw output that might even not be in the correct order of execution... :-\ |
Signed-off-by: Stephane Bouchet <[email protected]>
Signed-off-by: Stephane Bouchet <[email protected]>
Signed-off-by: Stephane Bouchet <[email protected]>
yes, I tried to use the -e to have extra output, but I only get the first stack entry, that is the exact output from the test report. :(
|
Signed-off-by: Stephane Bouchet <[email protected]>
7290566
to
c821ffb
Compare
Noticed usage reporting is not disabled which we were doing on Jenkins, not sure this is the cause of the failed tests |
Signed-off-by: Stephane Bouchet <[email protected]>
I can see it is correctly disabled, using-Dusage_reporting_enabled=false : |
@koentsje: in my last attempt i added some try/catch to one of the failing test and I got a better stack :
so it looks like all the IllegalArgumentExceptions are coming from here? |
Signed-off-by: Stephane Bouchet <[email protected]>
converted to draft as i'm trying to identify the cause. it seems related to the locale used by the image that is not supported. locally,n the Currency/Locale is ok. (Currency=EUR, Locale=fr_FR) |
ok, i'm going somewhere.. |
62502a2
to
b43b9b9
Compare
Signed-off-by: Stephane Bouchet <[email protected]>
b43b9b9
to
63c1f02
Compare
i have the week off, so I am only looking from far at this... in any case thanks for digging into it ;-) |
Signed-off-by: Stephane Bouchet <[email protected]>
Signed-off-by: Stephane Bouchet <[email protected]>
Signed-off-by: Stephane Bouchet <[email protected]>
oh boy, w00t w00t !!! thanks for all your efforts in any case, very much appreciated :-) |
@sbouchet From my point of view the changes look good. Though I am curious what is default system locale setup. Otherwise nice job. |
it was set to something like "C.UTF-8" |
Signed-off-by: Stephane Bouchet [email protected]