You don't know when pirates attack.
InspectLoadedCargo:210
if (( c.loadLocation.getCode().equals( "SOMGQ" ) &&
new Random().nextInt( 100 ) < 20 ) ||
(
carrierMovement.arrivalLocation().get().getCode().equals( "SOMGQ" ) &&
new Random().nextInt( 100 ) < 15 ))
{
so test shouldn't throw exception
fix was pushed.
- Tibor
On Mon, May 21, 2012 at 10:42 AM, Paul Merlin <[email protected]> wrote:
> Niclas Hedhman a écrit :
>
>> I just got this remarkable Testcase failure;
>>
>> "Cargo 'Naive' was hijacked. MOCKUP MESSAGE TO CARGO OWNER: We're
>> sorry to inform you that your cargo 'Naive' was hijacked. Please
>> contact your insurance company."
>>
>> Which insurance company? I could really have used my 'Naive'...
>
> It seems that this test (InspectLoadedCargoTest.riskZoneDeparture)
> fails intermittently.
>
> I got this failure message:
>
> Cargo 'Hopeful' was hijacked.
>
> MOCKUP MESSAGE TO CARGO OWNER: We're sorry to inform you that your
> cargo 'Hopeful' was hijacked. Please contact your insurance company.
>
> Last build on the CI server failed too.
> See
> https://qi4j.ci.cloudbees.com/job/qi4j-sdk.develop.tests.jdk6-sun/8/testReport/junit/com.marcgrue.dcisample_b.context.test.handling.inspection.event/InspectLoadedCargoTest/riskZoneDestination/
>
> @Tibor: the dci-cargo sample codebase should be fresh for you, could
> you take a look please?
>
>
> /Paul
>
>
>
> _______________________________________________
> qi4j-dev mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
