You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Ankur Goenka <go...@google.com> on 2019/05/14 20:42:46 UTC
All validates runner tests seems to be broken.
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
Re: All validates runner tests seems to be broken.
Posted by Michael Luckey <ad...@gmail.com>.
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 <ap...@google.com> 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 <go...@google.com>
> *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
>>
>
Re: All validates runner tests seems to be broken.
Posted by Andrew Pilloud <ap...@google.com>.
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 <go...@google.com>
*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
>
Re: All validates runner tests seems to be broken.
Posted by Ankur Goenka <go...@google.com>.
It seems to be related.
I will try to rerun the seed job.
*From: *Lukasz Cwik <lc...@google.com>
*Date: *Tue, May 14, 2019 at 1:52 PM
*To: *dev
Its likely related to the rename done in
> https://github.com/apache/beam/commit/f198de033824949eb66ea533ae8a40b8dd8cd7fe#diff-2bb618406f7ee4470a48343283f368a2
> Kenn is tracking a different issue related to publishing being broken
> in BEAM-7302 which he has a fix for in
> https://github.com/apache/beam/pull/8577
>
> I suspect there will be a few of these gotchas.
>
>
> *From: *Ankur Goenka <go...@google.com>
> *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
>>
>
Re: All validates runner tests seems to be broken.
Posted by Lukasz Cwik <lc...@google.com>.
Its likely related to the rename done in
https://github.com/apache/beam/commit/f198de033824949eb66ea533ae8a40b8dd8cd7fe#diff-2bb618406f7ee4470a48343283f368a2
Kenn is tracking a different issue related to publishing being broken
in BEAM-7302 which he has a fix for in
https://github.com/apache/beam/pull/8577
I suspect there will be a few of these gotchas.
*From: *Ankur Goenka <go...@google.com>
*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
>
Re: All validates runner tests seems to be broken.
Posted by Ankur Goenka <go...@google.com>.
yup, running the seed job.
@Alan Myrvold <am...@google.com> The other tests are also failing which
do not have a typo,
*From: *Andrew Pilloud <ap...@google.com>
*Date: *Tue, May 14, 2019 at 2:02 PM
*To: *dev
So it sounds like a number of the failures are related to a single jenkins
> config for all branches. This means you can't test the release branch if
> the targets change after it is cut. One possibility: do "Run Seed Job" on
> the release branch and kick off all the tests right after that finishes.
> Then do "Run Seed Job" after they all start on head again to restore the
> config.
>
> Andrew
>
> *From: *Alan Myrvold <am...@google.com>
> *Date: *Tue, May 14, 2019 at 1:59 PM
> *To: * <de...@beam.apache.org>
>
> That is a typo added in https://github.com/apache/beam/pull/8194
>>
>> https://github.com/apache/beam/commit/1e7ea0da5073566c3fa26dbc1105105fbe6043ae#diff-9591f0d06e82e711681fd77ed287578b
>>
>> *From: *Ankur Goenka <go...@google.com>
>> *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
>>>
>>
Re: All validates runner tests seems to be broken.
Posted by Michael Luckey <ad...@gmail.com>.
Created reverting PR
https://github.com/apache/beam/pull/8581
You might approve and merge.
On Tue, May 14, 2019 at 11:19 PM Ankur Goenka <go...@google.com> wrote:
> Ahh, I see. Good point.
> so shall we revert test-infra?
>
> *From: *Alan Myrvold <am...@google.com>
> *Date: *Tue, May 14, 2019 at 2:16 PM
> *To: * <de...@beam.apache.org>
>
> Other ones are failing on the branch due to the 2.13.0 branch not having
>> https://github.com/apache/beam/pull/8194, and the seed job running from
>> master.
>>
>> *From: *Michael Luckey <ad...@gmail.com>
>> *Date: *Tue, May 14, 2019 at 2:13 PM
>> *To: * <de...@beam.apache.org>
>>
>> Unfortunately, I missed the fact that seed job triggers automatically.
>>>
>>> Yes, you need to run the seed job on your branch to replace the old
>>> commands.
>>>
>>> We might consider resetting to legacy commands, i.e. revert ./test-infra
>>> folder. What do you think?
>>>
>>> On Tue, May 14, 2019 at 11:02 PM Andrew Pilloud <ap...@google.com>
>>> wrote:
>>>
>>>> So it sounds like a number of the failures are related to a single
>>>> jenkins config for all branches. This means you can't test the release
>>>> branch if the targets change after it is cut. One possibility: do "Run Seed
>>>> Job" on the release branch and kick off all the tests right after that
>>>> finishes. Then do "Run Seed Job" after they all start on head again to
>>>> restore the config.
>>>>
>>>> Andrew
>>>>
>>>> *From: *Alan Myrvold <am...@google.com>
>>>> *Date: *Tue, May 14, 2019 at 1:59 PM
>>>> *To: * <de...@beam.apache.org>
>>>>
>>>> That is a typo added in https://github.com/apache/beam/pull/8194
>>>>>
>>>>> https://github.com/apache/beam/commit/1e7ea0da5073566c3fa26dbc1105105fbe6043ae#diff-9591f0d06e82e711681fd77ed287578b
>>>>>
>>>>> *From: *Ankur Goenka <go...@google.com>
>>>>> *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
>>>>>>
>>>>>
Re: All validates runner tests seems to be broken.
Posted by Ankur Goenka <go...@google.com>.
Ahh, I see. Good point.
so shall we revert test-infra?
*From: *Alan Myrvold <am...@google.com>
*Date: *Tue, May 14, 2019 at 2:16 PM
*To: * <de...@beam.apache.org>
Other ones are failing on the branch due to the 2.13.0 branch not having
> https://github.com/apache/beam/pull/8194, and the seed job running from
> master.
>
> *From: *Michael Luckey <ad...@gmail.com>
> *Date: *Tue, May 14, 2019 at 2:13 PM
> *To: * <de...@beam.apache.org>
>
> Unfortunately, I missed the fact that seed job triggers automatically.
>>
>> Yes, you need to run the seed job on your branch to replace the old
>> commands.
>>
>> We might consider resetting to legacy commands, i.e. revert ./test-infra
>> folder. What do you think?
>>
>> On Tue, May 14, 2019 at 11:02 PM Andrew Pilloud <ap...@google.com>
>> wrote:
>>
>>> So it sounds like a number of the failures are related to a single
>>> jenkins config for all branches. This means you can't test the release
>>> branch if the targets change after it is cut. One possibility: do "Run Seed
>>> Job" on the release branch and kick off all the tests right after that
>>> finishes. Then do "Run Seed Job" after they all start on head again to
>>> restore the config.
>>>
>>> Andrew
>>>
>>> *From: *Alan Myrvold <am...@google.com>
>>> *Date: *Tue, May 14, 2019 at 1:59 PM
>>> *To: * <de...@beam.apache.org>
>>>
>>> That is a typo added in https://github.com/apache/beam/pull/8194
>>>>
>>>> https://github.com/apache/beam/commit/1e7ea0da5073566c3fa26dbc1105105fbe6043ae#diff-9591f0d06e82e711681fd77ed287578b
>>>>
>>>> *From: *Ankur Goenka <go...@google.com>
>>>> *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
>>>>>
>>>>
Re: All validates runner tests seems to be broken.
Posted by Alan Myrvold <am...@google.com>.
Other ones are failing on the branch due to the 2.13.0 branch not having
https://github.com/apache/beam/pull/8194, and the seed job running from
master.
*From: *Michael Luckey <ad...@gmail.com>
*Date: *Tue, May 14, 2019 at 2:13 PM
*To: * <de...@beam.apache.org>
Unfortunately, I missed the fact that seed job triggers automatically.
>
> Yes, you need to run the seed job on your branch to replace the old
> commands.
>
> We might consider resetting to legacy commands, i.e. revert ./test-infra
> folder. What do you think?
>
> On Tue, May 14, 2019 at 11:02 PM Andrew Pilloud <ap...@google.com>
> wrote:
>
>> So it sounds like a number of the failures are related to a single
>> jenkins config for all branches. This means you can't test the release
>> branch if the targets change after it is cut. One possibility: do "Run Seed
>> Job" on the release branch and kick off all the tests right after that
>> finishes. Then do "Run Seed Job" after they all start on head again to
>> restore the config.
>>
>> Andrew
>>
>> *From: *Alan Myrvold <am...@google.com>
>> *Date: *Tue, May 14, 2019 at 1:59 PM
>> *To: * <de...@beam.apache.org>
>>
>> That is a typo added in https://github.com/apache/beam/pull/8194
>>>
>>> https://github.com/apache/beam/commit/1e7ea0da5073566c3fa26dbc1105105fbe6043ae#diff-9591f0d06e82e711681fd77ed287578b
>>>
>>> *From: *Ankur Goenka <go...@google.com>
>>> *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
>>>>
>>>
Re: All validates runner tests seems to be broken.
Posted by Michael Luckey <ad...@gmail.com>.
Unfortunately, I missed the fact that seed job triggers automatically.
Yes, you need to run the seed job on your branch to replace the old
commands.
We might consider resetting to legacy commands, i.e. revert ./test-infra
folder. What do you think?
On Tue, May 14, 2019 at 11:02 PM Andrew Pilloud <ap...@google.com> wrote:
> So it sounds like a number of the failures are related to a single jenkins
> config for all branches. This means you can't test the release branch if
> the targets change after it is cut. One possibility: do "Run Seed Job" on
> the release branch and kick off all the tests right after that finishes.
> Then do "Run Seed Job" after they all start on head again to restore the
> config.
>
> Andrew
>
> *From: *Alan Myrvold <am...@google.com>
> *Date: *Tue, May 14, 2019 at 1:59 PM
> *To: * <de...@beam.apache.org>
>
> That is a typo added in https://github.com/apache/beam/pull/8194
>>
>> https://github.com/apache/beam/commit/1e7ea0da5073566c3fa26dbc1105105fbe6043ae#diff-9591f0d06e82e711681fd77ed287578b
>>
>> *From: *Ankur Goenka <go...@google.com>
>> *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
>>>
>>
Re: All validates runner tests seems to be broken.
Posted by Andrew Pilloud <ap...@google.com>.
So it sounds like a number of the failures are related to a single jenkins
config for all branches. This means you can't test the release branch if
the targets change after it is cut. One possibility: do "Run Seed Job" on
the release branch and kick off all the tests right after that finishes.
Then do "Run Seed Job" after they all start on head again to restore the
config.
Andrew
*From: *Alan Myrvold <am...@google.com>
*Date: *Tue, May 14, 2019 at 1:59 PM
*To: * <de...@beam.apache.org>
That is a typo added in https://github.com/apache/beam/pull/8194
>
> https://github.com/apache/beam/commit/1e7ea0da5073566c3fa26dbc1105105fbe6043ae#diff-9591f0d06e82e711681fd77ed287578b
>
> *From: *Ankur Goenka <go...@google.com>
> *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
>>
>
Re: All validates runner tests seems to be broken.
Posted by Alan Myrvold <am...@google.com>.
That is a typo added in https://github.com/apache/beam/pull/8194
https://github.com/apache/beam/commit/1e7ea0da5073566c3fa26dbc1105105fbe6043ae#diff-9591f0d06e82e711681fd77ed287578b
*From: *Ankur Goenka <go...@google.com>
*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
>