To clarify: These failures are expected. And not much we can do abou. It is just that I did forget about the consequences for the ongoing release. (Sorry again, Ankur!)
Apart from that, testing was done on local Jenkins setup to not mess with the global configuration. As this would have blocked any other dev trying to run Jenkins task. Obviously, I messed it up by letting that typo pass. Sorry for that. We probably run into more issues as soon we revert the revert done today. In hindsight, I totally agree it was a mistake to not split it up directly. It should be possible to run the seed job as soon as PRs are rebased on branches containing the changes of BEAM-4046 without impacting all other work. Best, michel On Wed, May 15, 2019 at 12:37 AM Andrew Pilloud <[email protected]> wrote: > The specific issue in your text appears to be a typo introduced in > https://github.com/apache/beam/pull/8194 While that PR ran a bunch of > tests, I didn't see a reference to "Run Seed Job", which means it didn't > actually test the code in the change. > > I expect not all the failures are the same as that typo only appears on > one job, but it seems problematic that we merged a major jenkins refactor > without any testing. > > Andrew > > *From: *Ankur Goenka <[email protected]> > *Date: *Tue, May 14, 2019 at 1:43 PM > *To: *dev > > Hi, >> >> Following tests seems to be broken because of "Project 'unners' not found >> in root project 'beam'." >> The command getting executed on Jenkins is >> gradlew --continue --max-workers=12 -Dorg.gradle.jvmargs=-Xms2g >> -Dorg.gradle.jvmargs=-Xmx4g :unners:samza:validatesRunner >> causing the failure. >> The same is happening on the master >> https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza_PR/19/console >> >> Are we making any changes to jenins parsing scripts? >> >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex_PR/20/> >> [image: @asfgit] <https://github.com/asfgit> >> Apache Flink Runner ValidatesRunner Tests — FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink_PR/63/> >> [image: @asfgit] <https://github.com/asfgit> >> Apache Gearpump Runner ValidatesRunner Tests — FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump_PR/16/> >> [image: @asfgit] <https://github.com/asfgit> >> Apache Samza Runner ValidatesRunner Tests — FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza_PR/17/> >> [image: @asfgit] <https://github.com/asfgit> >> Apache Spark Runner ValidatesRunner Tests — FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark_PR/73/> >> [image: @asfgit] <https://github.com/asfgit> >> Google Cloud Dataflow Runner PortabilityApi ValidatesRunner Tests — >> FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_PortabilityApi_Dataflow_PR/39/> >> [image: @asfgit] <https://github.com/asfgit> >> Google Cloud Dataflow Runner Python ValidatesContainer Tests — FAILURE >> Details <https://builds.apache.org/job/beam_PostCommit_Py_ValCont_PR/54/> >> [image: @asfgit] <https://github.com/asfgit> >> Google Cloud Dataflow Runner Python ValidatesRunner Tests — FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow_PR/79/> >> [image: @asfgit] <https://github.com/asfgit> >> Google Cloud Dataflow Runner ValidatesRunner Tests — FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_PR/59/> >> [image: @asfgit] <https://github.com/asfgit> >> Java Flink PortableValidatesRunner Batch Tests — FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch_PR/50/> >> [image: @asfgit] <https://github.com/asfgit> >> Java Flink PortableValidatesRunner Streaming Tests — FAILURE >> Details >> <https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Streaming_PR/77/> >> >> Thanks, >> Ankur >> >
