ant prepare-release-no-sign fails intermittently [LUCENE-7033]

[asfimport]

Mike reported this on the mailing list. This is fully reproducible, you just need to run it twice:

cd lucene
# succeeds
ant prepare-release-no-sign
# fails
ant prepare-release-no-sign

The problem is with this target that runs conditionally:

  <target name="-unpack-lucene-tgz" unless="lucene.tgz.unpack.dir.exists">
    <antcall target="-ensure-lucene-tgz-exists" inheritall="false">
      <propertyset refid="uptodate.and.compiled.properties"/>
    </antcall>
    <mkdir dir="${lucene.tgz.unpack.dir}"/>
    <untar compression="gzip" src="${lucene.tgz.file}" dest="${lucene.tgz.unpack.dir}">
      <patternset refid="patternset.lucene.solr.jars"/>
    </untar>
  </target>

I attach a diff from the two runs – you can see the second one skipped this task and then cleaned the output folder, which doesn't make sense.

I don't know how to fix, but I think it's this.

---

Migrated from LUCENE-7033 by Dawid Weiss (@dweiss), updated Feb 20 2016 Attachments: capture-2.png

[asfimport]

Michael McCandless (@mikemccand) (migrated from JIRA)

There was a long email thread that degenerated into a gitstorm about this issue, and I couldn't tell: is this now solved?

[asfimport]

Dawid Weiss (@dweiss) (migrated from JIRA)

Jenkins configuration has been fixed to clean up before every build, but the source of the problem (non-determinism in the build file – the output depends on whether build folder is available or not) has not been fixed I believe.