# Dry run and actual order differ

**URL:** <https://discuss.gradle.org/t/dry-run-and-actual-order-differ/26999>\
**Category:** Help/Discuss\
**Created:** [May 18, 2018, 6:03pm UTC](https://discuss.gradle.org/t/dry-run-and-actual-order-differ/26999 "2018-05-18T18:03:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nik9000](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/nik9000/32/3239_2.png) [@nik9000](https://discuss.gradle.org/u/nik9000)\
**Post date:** [May 18, 2018, 6:03pm UTC](https://discuss.gradle.org/t/dry-run-and-actual-order-differ/26999/1 "2018-05-18T18:03:14Z")

</div>

I’m working on a [change](https://github.com/elastic/elasticsearch/pull/30728) to our Gradle build that requires fairly specific task ordering and I’m seeing a difference between the ordering of tasks when I do a dry run vs when I run for real. The “for real” run executes in the correct order but the “dry run” doesn’t.

The incorrect [dry run](https://gist.github.com/nik9000/3bfe70abfe24f03a677b9d2e9964cfa8) has:

```gradle
:qa:rolling-upgrade:v6.4.0-SNAPSHOT#oneThirdUpgradedTestCluster#start SKIPPED
... snip ...
:qa:rolling-upgrade:v6.4.0-SNAPSHOT#oneThirdUpgradedTestCluster#configure SKIPPED

```

The correct [real run](https://gist.github.com/nik9000/ebffb56b09c82dbfeeb852b89fef2574) has:

```gradle
:qa:rolling-upgrade:v6.4.0-SNAPSHOT#oneThirdUpgradedTestCluster#configure (Thread[Task worker for ':',5,main]) completed. Took 0.001 secs.
:qa:rolling-upgrade:v6.4.0-SNAPSHOT#oneThirdUpgradedTestCluster#start (Thread[Task worker for ':',5,main]) completed. Took 0.019 secs.

```

I played around with it for a while, printing out the dependencies all over the place and `v6.4.0-SNAPSHOT#oneThirdUpgradedTestCluster#start` always depends on `v6.4.0-SNAPSHOT#oneThirdUpgradedTestCluster#configure` when I look, but dry run is still doing them out of order. Any idea what is going on?