Jon triggered a run on tck.work for that branch [1] (thx!!) and we have only 4 regressions from the upgrade.
Will have a look into those failures and see, if I can find out something useful. [1] https://tck.work/tomee/tests?path=com.sun.ts.tests.jaxrs&build=1692359054645&status=FAILED Am Freitag, dem 18.08.2023 um 11:47 +0200 schrieb Richard Zowalla: > Now I actually also ran my local setup again with 9.1.1-SNAPSHOT > which > we know passes the TCK for EE 9.1. > > The result is: 2708 | 95 > > This suggests that my local setup is a bit wonky as the same tests > are > failing ;) > > It would be great if someone could take my CXF4 branch and run the EE > 9.1 TCK against it once. > > Gruß > Richard > > Am Donnerstag, dem 17.08.2023 um 17:29 +0200 schrieb Richard Zowalla: > > > Hi, > > > > > > I've been doing some work to get rid of our cxf-shade and migrate > > > to > > > cxf 4.0.2. The branch is here: [1]. > > > > > > Our own build is in progess and I expect some failures due to > > > missed > > > dependencies in test setups: [2] > > > > > > I did run the jaxrs part of the TCK (ee91) against my branch > > > locally > > > and it looks promising but (as expected) we have some TCK > > > regressions > > > (*meh*): > > > > > > Completed running 2803 tests (1:34:15.098): > > > > > > Passed: 2706 > > > Failed: 97 > > > Errors: 0 > > > > > > > > > In the past, my local tck setup sometimes failed for tests, which > > > > > > > were > > > ok on other systems. Maybe someone can confirm, that these tests > > > are > > > actually failing for them too? Here is my list: [3] > > > > > > For reference I did run > > > > > > rm -rf target/ && ./runtests -Dhttps.protocols=TLSv1.1,TLSv1.2 -- > > > ee91 > - > > > j --env -nc -c -w tomee-plume com.sun.ts.tests.jaxrs > > > > > > Any feedback welcome. > > > > > > Gruß > > > Richard > > > > > > > > > > > > > > > [1] https://github.com/rzo1/tomee/tree/cxf4 > > > [2] > > > https://ci-builds.apache.org/job/Tomee/job/pull-request-manual/15 > > > [3] https://gist.github.com/rzo1/efbfbf568e7101842d3ffab2fdb38a3b >
signature.asc
Description: This is a digitally signed message part
