Most likely this isn't a problem with a particular test but with Gradle's testing infrastructure. It would be very valuable if you could provide a build that allows to reproduce the problem. What are your test settings? Do you run tests in parallel?

I'll try and put together a test that causes this issue. But where do I find the test id's that Gradle assigns to each test? When it says:

I couldn't find test with id: 1.108

How do I find out which test it assigned as 1.108?

Just a friendly reminder to see about scheduling this for 1.0-milestone-8, so it doesn't slip through the cracks. Thanks!

@chris, we're working on this. It's more or less fixed in master.

Right; Szczepan pointed me at a snapshot and I'm trying it out now.

I'm now running successfully against gradle-1.0-milestone-8-20120112000036+0100. I've got a build plan in a loop running every fifteen minutes to see if we hit the intermittent "couldn't find test with id" error. If it crops back up, I'll comment here.

In the meantime, we are still getting warnings like these – it seems related:

Failed to parse test result file "TEST-org.springframework.integration.amqp.config.OutboundGatewayIntegrationTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.aggregator.AggregatorTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.aggregator.ConcurrentAggregatorTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.aggregator.scenarios.AggregationResendTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.core.MessageIdGenerationTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.dispatcher.AggregateMessageDeliveryExceptionTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.gateway.MessagingGatewayTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.history.MessageHistoryIntegrationTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.store.MessageGroupQueueTests.xml"
Failed to parse test result file "TEST-org.springframework.integration.feed.config.FeedInboundChannelAdapterParserTests.xml"
...

See https://build.springsource.org/browse/INT-BUILD-JOB2-11

Any idea why? And how to get rid of them?

Thanks for the fixes so far!

As mentioned above, I put https://build.springsource.org/browse/INT-BUILD/ in a loop against the latest m8 snapshot, and after twenty or so builds, have seen no failures. So it looks like this issue is indeed taken care of. Thanks!

Any comment on the "Failed to parse test result" entries would still be appreciated, as they are still occurring throughout all those recent runs.

Looking at it...

It appears this exception comes from Bamboo. It is a problem because you don't have reports available for those tests in Bamboo :/ How can I get hold of those 'invalid' xmls?

Attached all TEST-* files from the most recent run of INT-BUILD

All files look good to me, they contain all data, they are valid xml, etc. I don't know why bamboo refuses to parse them. Perhaps something else has changed in the environment that might introduce this behavior? Are you sure this error wasn't there before? Might be worth looking closer into bamboo logs or ask the atlassian dudes why a valid report cannot be parsed (or suggest them to add some information to the warning why the file cannot be parsed).

It's hard to be 100% sure these days but I'm reasonably confident my change couldn't break the xml generation E.g. implementation wise the xml generator is one TestResultProcessor and I was changing a different TestResultProcessor.

Are you sure this error wasn't there before?

Actually, looking back in the build logs, these warnings have been happening for quite some time. Here's one from November: https://build.springsource.org/browse/INT-MASTER-JOB1-198

So it appears that this really is a separate issue from the "couldn't find test with id" problem that was addressed here.

The SI guys are all watching this issue, so I'll pass your advice above along to them:

[It] might be worth looking closer into bamboo logs or ask the atlassian dudes why a valid report cannot be parsed (or suggest them to add some information to the warning why the file cannot be parsed).

This is something that might be worth taking up with our Atlassian support contract, but in the meantime, it's clearly benign with regard to the SI build, and seems only to happen under CI. Probably not so critical, then.

Thanks, Szczepan! Please resolve at will; we're looking good now.

Cool