Parallel execution reports incorrect task failure

Old Forum Archive
1

Summary -------------- It seems that if a task in a project depends on a task and a subproject task (i.e. from another project),

when running gradle in parallel execution (and the subprojects task fails) gradle reports the incorrect task as failing?

This seems to be because gradle will assign 2 executors one to both projects, however when reporting the error it all gets confused, and seems to report based on alphabetic order? :frowning:

gradle top >> :b:b1 FAILED

gradle --parallel top >> a1 FAILED

Am I missing some concept here? or does this just not work “correctly”

Thanks

/Ian.

Details ----------------------- project structure -A --|–B

project A has task top and a1 project B has b1

i.e.

Project A task a1 << {

printf “a1: this one works\n” } task top( dependsOn: [a1, “:b:b1”]) << {

printf “top\n” }

Project B

task b1 << {

printf “b1\n”

throw new GradleException(“This one fails”)

}

------------------------------------------------------------ Gradle 1.12 ------------------------------------------------------------

Build time:

2014-04-29 09:24:31 UTC Build number: none Revision:

a831fa866d46cbee94e61a09af15f9dd95987421

Groovy:

1.8.6 Ant:

Apache Ant™ version 1.9.3 compiled on December 23 2013 Ivy:

2.2.0 JVM:

1.7.0_09 (Oracle Corporation 23.5-b02) OS:

Windows 8 6.2 amd64

2

This works as expected with Gradle 2.3. Would you mind trying with that version?

3

Thanks for trying, yep it works in 2.3

Trying different versions it seems that it was fixed between v2.0 and v2.1. now to convince the project to upgrade (though we have stuff that only works before gradle 2 :frowning: )