Hi Okay I think I have it fixed. So lets see next CI build
On Sat, Aug 3, 2019 at 10:00 AM Claus Ibsen <claus.ib...@gmail.com> wrote: > > Hi > > Okay so there are some unit test errors (approx 35) on CI after this > change. I will take a look over the weekend/monday. > I had a hunch that maybe something would be affected as the test > happens early now vs late. > > On Fri, Aug 2, 2019 at 5:01 PM Claus Ibsen <claus.ib...@gmail.com> wrote: > > > > Hi > > > > https://issues.apache.org/jira/browse/CAMEL-12003 > > > > When you use assertIsSatisifed with mock endpoints during testing then > > they will now fail fast if a message arrived that would cause an > > expectation to fail, and there are still more messages expected. > > > > Before the mock endpoint would only validate expectations when the > > number of expected message had arrived. > > > > This is default enabled and you can turn it off by setting > > failFast=false on the mock endpoint in your routes - to use 2.x > > behaviour. But I dont expect people to want to use this (but just in > > case). > > > > > > -- > > Claus Ibsen > > ----------------- > > http://davsclaus.com @davsclaus > > Camel in Action 2: https://www.manning.com/ibsen2 > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
