Yes, guessed so as well. I simply removed the space, added a few cleanup calls and now this test is green.
Still we seem to have a problem with db setup on Jenkins. Locally all is green now. 2.4.x is also green. Have to compare the tests on Jenkins w my local box. LieGrue, Strub > Am 21.08.2016 um 20:36 schrieb Romain Manni-Bucau <[email protected]>: > > Depends the db since some will quote this name or trim it. In anyway not > what we want for basic/atomic test like this one. > > Le 21 août 2016 18:14, "Mark Struberg" <[email protected]> a écrit : > >> ouch >> >> >>> @StoredProcedureParameter(name = "P ", type = Integer.class, mode = >> INOUT) >> >> >> Notice the space after the P... ;) >> >> Should this work? Means should there be an internal trim? >> >> LieGrue, >> strub >> >> >> >> >>> On Sunday, 21 August 2016, 17:19, Mark Struberg >> <[email protected]> wrote: >>>> 2.4.x is now back to green again. >>> >>> Working on trunk right now. >>> >>> I think TestStoredProcedure is the last blocker. >>> This is a new test and I have to read the JPA-2.1 spec for digging a bit >> deeper. >>> >>> LieGrue, >>> strub >>> >>> >>> >>> >>> >>> >>>> On Friday, 19 August 2016, 22:19, Mark Struberg >>> <[email protected]> wrote: >>>>> Good evening! >>>> >>>> We have 11 errors in the 2.4.x and trunk builds right now. >>>> Somehow most tests did not run lately. Not sure why they ever did, >> because >>>> **/*.class was excluded… >>>> >>>> Now the tests run again and they show us a long nose ;) >>>> >>>> Will try to look at a few of them over the weekend, so we can move >> forward. >>>> >>>> Anyone is happy to help! >>>> >>>> LieGrue, >>>> strub >>>> >>> >>
