6.7 BWC builds are failing due to missing directory

[danielmitterdorfer]

We see the CI build https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+bwc-tests/ failing all the time with:

06:23:30 Execution failed for task ':x-pack:qa:full-cluster-restart:with-system-key:v5.0.0#oldClusterTestRunner'.
06:23:30 > /var/lib/jenkins/workspace/elastic+elasticsearch+6.7+bwc-tests/x-pack/qa/full-cluster-restart/with-system-key/build/classes/java/test does not exist.

This failure happens since build 253. Analyzing the new commits in that build, f2e3978 (from #41026) stands out. To me it seems as if we mix up test/java (expected) and java/test (actual) in the directory structure.

[elasticmachine]

Pinging @elastic/es-core-infra

[alpar-t]

interestingly, doesn't reproduce locally with ./gradlew -p x-pack/qa/full-cluster-restart check

[droberts195]

This is still failing, for example:

• https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+bwc-tests/303/console
• https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+bwc-tests/304/console

I reproduced it on the current 6.7 branch (a62de13) on a Linux server in the London office using:

 ./gradlew :x-pack:qa:full-cluster-restart:with-system-key:v5.0.0#bwcTest

[alpar-t]

I managed to reproduce it after a ./gradlew clean

[alpar-t]

It doesn't reproduce without f2e3978 from a quick look it seems that the class file are not getting generated for bwc tests as the tasks to do so are not wired in.
@mark-vieira any ideas ? I don't mind digging into this, but maybe it's something immediately obvious to you since it relates to one of your changes.

[hendrikmuhs]

still an issue: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+bwc-tests/316/console

[bizybot]

still an issue: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+bwc-tests/309/console

[davidkyle]

still an issue https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.7+bwc-tests/332/console

[mark-vieira]

Taking a look at this today.