Flaky test issue report (59)

[Beam Jira Bot]

This is your daily summary of Beam's current flaky tests 
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake)

These are P1 issues because they have a major negative impact on the community 
and make it hard to determine the quality of the software.

https://issues.apache.org/jira/browse/BEAM-14543: 
beam_PostCommit_Java_ValidatesRunner_Samza Failing (created 2022-06-01)
https://issues.apache.org/jira/browse/BEAM-14459: Docker Snapshots failing 
to be published since April 14th (created 2022-05-11)
https://issues.apache.org/jira/browse/BEAM-14410: FnRunnerTest with 
non-trivial (order 1000 elements) numpy input flakes in non-cython environment 
(created 2022-05-04)
https://issues.apache.org/jira/browse/BEAM-14407: Jenkins worker sometimes 
crashes while running Python Flink pipeline (created 2022-05-04)
https://issues.apache.org/jira/browse/BEAM-14367: Flaky timeout in github 
Python unit test action 
StatefulDoFnOnDirectRunnerTest.test_dynamic_timer_clear_then_set_timer (created 
2022-04-26)
https://issues.apache.org/jira/browse/BEAM-14349: GroupByKeyTest BasicTests 
testLargeKeys100MB flake (on ULR) (created 2022-04-21)
https://issues.apache.org/jira/browse/BEAM-14276: 
beam_PostCommit_Java_DataflowV2 failures parent bug (created 2022-04-07)
https://issues.apache.org/jira/browse/BEAM-14269: 
PulsarIOTest.testReadFromSimpleTopic is very flaky (created 2022-04-06)
https://issues.apache.org/jira/browse/BEAM-14263: 
beam_PostCommit_Java_DataflowV2, testBigQueryStorageWrite30MProto failing 
consistently (created 2022-04-05)
https://issues.apache.org/jira/browse/BEAM-14252: 
beam_PostCommit_Java_DataflowV1 failing with a variety of flakes and errors 
(created 2022-04-05)
https://issues.apache.org/jira/browse/BEAM-14216: Multiple XVR Suites 
having similar flakes simultaneously (created 2022-03-31)
https://issues.apache.org/jira/browse/BEAM-14174: Flink Tests failure :  
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.beam.runners.core.construction.SerializablePipelineOptions  (created 
2022-03-24)
https://issues.apache.org/jira/browse/BEAM-14172: beam_PreCommit_PythonDocs 
failing (jinja2) (created 2022-03-24)
https://issues.apache.org/jira/browse/BEAM-13952: Dataflow streaming tests 
failing new AfterSynchronizedProcessingTime test (created 2022-02-15)
https://issues.apache.org/jira/browse/BEAM-13859: Test flake: 
test_split_half_sdf (created 2022-02-09)
https://issues.apache.org/jira/browse/BEAM-13850: 
beam_PostCommit_Python_Examples_Dataflow failing (created 2022-02-08)
https://issues.apache.org/jira/browse/BEAM-13822: GBK and CoGBK streaming 
Java load tests failing (created 2022-02-03)
https://issues.apache.org/jira/browse/BEAM-13810: Flaky tests: Gradle build 
daemon disappeared unexpectedly (created 2022-02-03)
https://issues.apache.org/jira/browse/BEAM-13809: beam_PostCommit_XVR_Flink 
flaky: Connection refused (created 2022-02-03)
https://issues.apache.org/jira/browse/BEAM-13797: Flakes: Failed to load 
cache entry (created 2022-02-01)
https://issues.apache.org/jira/browse/BEAM-13708: flake: 
FlinkRunnerTest.testEnsureStdoutStdErrIsRestored (created 2022-01-20)
https://issues.apache.org/jira/browse/BEAM-13575: Flink 
testParDoRequiresStableInput flaky (created 2021-12-28)
https://issues.apache.org/jira/browse/BEAM-13500: NPE in Flink Portable 
ValidatesRunner streaming suite (created 2021-12-21)
https://issues.apache.org/jira/browse/BEAM-13453: Flake in 
org.apache.beam.sdk.io.mqtt.MqttIOTest.testReadObject: Address already in use 
(created 2021-12-13)
https://issues.apache.org/jira/browse/BEAM-13393: GroupIntoBatchesTest is 
failing (created 2021-12-07)
https://issues.apache.org/jira/browse/BEAM-13367: 
[beam_PostCommit_Python36] [ 
apache_beam.io.gcp.experimental.spannerio_read_it_test] Failure summary 
(created 2021-12-01)
https://issues.apache.org/jira/browse/BEAM-13312: 
org.apache.beam.sdk.transforms.ParDoLifecycleTest.testTeardownCalledAfterExceptionInStartBundle
 is flaky in Java Spark ValidatesRunner suite  (created 2021-11-23)
https://issues.apache.org/jira/browse/BEAM-13311: 
org.apache.beam.sdk.transforms.ParDoLifecycleTest.testTeardownCalledAfterExceptionInProcessElementStateful
 is flaky in Java ValidatesRunner Flink suite. (created 2021-11-23)
https://issues.apache.org/jira/browse/BEAM-13237: 
org.apache.beam.sdk.transforms.CombineTest$WindowingTests.testWindowedCombineGloballyAsSingletonView
 flaky on Dataflow Runner V2 (created 2021-11-12)
https://issues.apache.org/jira/browse/BEAM-13025: pubsublite.ReadWriteIT 
flaky in beam_PostCommit_Java_DataflowV2   (created 2021-10-08)
https://issues.apache.org/jira/browse/BEAM-12928: beam_PostCommit_Python36 
- CrossLanguageSpannerIOTest - flakey failing (created 2021-09-21)

P1 issues report (77)

[Beam Jira Bot]

This is your daily summary of Beam's current P1 issues, not including flaky 
tests 
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake).

See https://beam.apache.org/contribute/jira-priorities/#p1-critical for the 
meaning and expectations around P1 issues.

https://issues.apache.org/jira/browse/BEAM-14558: Data missing when using 
CassandraIO.Read (created 2022-06-03)
https://issues.apache.org/jira/browse/BEAM-14543: 
beam_PostCommit_Java_ValidatesRunner_Samza Failing (created 2022-06-01)
https://issues.apache.org/jira/browse/BEAM-14459: Docker Snapshots failing 
to be published since April 14th (created 2022-05-11)
https://issues.apache.org/jira/browse/BEAM-14434: 
beam_LoadTests_Python_GBK_reiterate_Dataflow_Streaming failure (created 
2022-05-06)
https://issues.apache.org/jira/browse/BEAM-14421: 
--dataflowServiceOptions=use_runner_v2 is broken (created 2022-05-05)
https://issues.apache.org/jira/browse/BEAM-14390: Java license check is 
broken (created 2022-05-02)
https://issues.apache.org/jira/browse/BEAM-14364: 404s in BigQueryIO don't 
get output to Failed Inserts PCollection (created 2022-04-25)
https://issues.apache.org/jira/browse/BEAM-14291: DataflowPipelineResult 
does not raise exception for unsuccessful states. (created 2022-04-11)
https://issues.apache.org/jira/browse/BEAM-14276: 
beam_PostCommit_Java_DataflowV2 failures parent bug (created 2022-04-07)
https://issues.apache.org/jira/browse/BEAM-14275: SpannerWriteIT failing in 
beam PostCommit Java V1 (created 2022-04-07)
https://issues.apache.org/jira/browse/BEAM-14265: Flink should hold the 
watermark at the output timestamp for processing time timers (created 
2022-04-06)
https://issues.apache.org/jira/browse/BEAM-14263: 
beam_PostCommit_Java_DataflowV2, testBigQueryStorageWrite30MProto failing 
consistently (created 2022-04-05)
https://issues.apache.org/jira/browse/BEAM-14253: pubsublite.ReadWriteIT 
failing in beam_PostCommit_Java_DataflowV1 and V2 (created 2022-04-05)
https://issues.apache.org/jira/browse/BEAM-14239: Changing the output 
timestamp of a timer does not clear the previously set timer (created 
2022-04-04)
https://issues.apache.org/jira/browse/BEAM-14174: Flink Tests failure :  
java.lang.NoClassDefFoundError: Could not initialize class 
org.apache.beam.runners.core.construction.SerializablePipelineOptions  (created 
2022-03-24)
https://issues.apache.org/jira/browse/BEAM-14146: Python Streaming job 
failing to drain with BigQueryIO write errors (created 2022-03-22)
https://issues.apache.org/jira/browse/BEAM-14135: BigQuery Storage API 
insert with writeResult retry and write to error table (created 2022-03-20)
https://issues.apache.org/jira/browse/BEAM-13952: Dataflow streaming tests 
failing new AfterSynchronizedProcessingTime test (created 2022-02-15)
https://issues.apache.org/jira/browse/BEAM-13950: PVR_Spark2_Streaming 
perma-red (created 2022-02-15)
https://issues.apache.org/jira/browse/BEAM-13920: Beam x-lang Dataflow 
tests failing due to _InactiveRpcError (created 2022-02-10)
https://issues.apache.org/jira/browse/BEAM-13852: 
KafkaIO.read.withDynamicRead() doesn't pick up new TopicPartitions (created 
2022-02-08)
https://issues.apache.org/jira/browse/BEAM-13850: 
beam_PostCommit_Python_Examples_Dataflow failing (created 2022-02-08)
https://issues.apache.org/jira/browse/BEAM-13822: GBK and CoGBK streaming 
Java load tests failing (created 2022-02-03)
https://issues.apache.org/jira/browse/BEAM-13805: Simplify version override 
for Dev versions of the Go SDK. (created 2022-02-02)
https://issues.apache.org/jira/browse/BEAM-13747: Add integration testing 
for BQ Storage API  write modes (created 2022-01-26)
https://issues.apache.org/jira/browse/BEAM-13715: Kafka commit offset drop 
data on failure for runners that have non-checkpointing shuffle (created 
2022-01-21)
https://issues.apache.org/jira/browse/BEAM-13669: Install Python wheel and 
dependencies to local venv in SDK harness (created 2022-01-17)
https://issues.apache.org/jira/browse/BEAM-13487: WriteToBigQuery Dynamic 
table destinations returns wrong tableId (created 2021-12-17)
https://issues.apache.org/jira/browse/BEAM-13393: GroupIntoBatchesTest is 
failing (created 2021-12-07)
https://issues.apache.org/jira/browse/BEAM-13164: Race between member 
variable being accessed due to leaking uninitialized state via 
OutboundObserverFactory (created 2021-11-01)
https://issues.apache.org/jira/browse/BEAM-13132: WriteToBigQuery submits a 
duplicate BQ load job if a 503 error code is returned from googleapi (created 
2021-10-27)
https://issues.apache.org/jira/browse/BEAM-13087: 
apache_beam.runners.portability.fn_api_runner.translations_test.TranslationsTest.test_run_packable_combine_globally
 

Re: Jira -> GitHub Issues Migration (This Friday)

[Hector Miuler Malpica Gallegos]

The Issue *Type* the Jira is not imported as *label* in github :(, I think
it's important


*Hector Miuler Malpica Gallegos *



El vie, 3 jun 2022 a la(s) 10:14, Danny McCormick (dannymccorm...@google.com)
escribió:

> Hey Hector, they were just enabled (thanks @Valentyn Tymofieiev
>  for merging the PR).
>
> The existing Jiras should be migrated throughout the rest of the day -
> this will take a while due to GitHub rate limits, but it should definitely
> be done by the end of the weekend (and I expect significantly earlier). In
> the meantime, feel free to start opening issues at
> https://github.com/apache/beam/issues, and let me know if you see any
> issues with the migrated issues.
>
> Thanks,
> Danny
>
> On Fri, Jun 3, 2022 at 10:42 AM Hector Miuler Malpica Gallegos <
> miu...@gmail.com> wrote:
>
>> When will github issues be enabled?  I understood that it would be today
>>
>>
>>
>> *Hector Miuler Malpica Gallegos *
>>
>>
>>
>> El jue, 2 jun 2022 a la(s) 21:35, Hector Miuler Malpica Gallegos (
>> miu...@gmail.com) escribió:
>>
>>>
>>> hahaha!!! excuse me, I'm thinking in the flink project when read the
>>> last email, I do not know why.
>>>
>>>
>>> *Hector Miuler Malpica Gallegos *
>>>
>>>
>>>
>>> El jue, 2 jun 2022 a la(s) 18:04, Danny McCormick (
>>> dannymccorm...@google.com) escribió:
>>>
 Thanks for calling that out Hector - the migration will only migrate
 issues from the Beam project (that one is from the Flink project), so I
 don't think it should be an issue.

 Thanks,
 Danny

 On Thu, Jun 2, 2022 at 6:38 PM Hector Miuler Malpica Gallegos <
 miu...@gmail.com> wrote:

> This migration includes the issues of the component `Kubernetes
> Operator` ? like this issue FLINK-27820
>  ? this issues
> correspond to the repository
> https://github.com/apache/flink-kubernetes-operator, keep it in mind.
>
>
> *Hector Miuler Malpica Gallegos *
>
>
>
> El jue, 2 jun 2022 a la(s) 12:33, Danny McCormick (
> dannymccorm...@google.com) escribió:
>
>> Given the consensus here, I updated the tool to do this. This means
>> that we won't update the JIRAs to be read-only until after the migration 
>> is
>> complete. I'll rerun the tool if any extra jiras come in during the
>> intervening period. The tool will also still write the mapping to the 
>> file
>> in case there are unforeseen issues so that we can backfill if needed.
>>
>> Thanks for the suggestion and followup Brian, Ahmet, and Alexey.
>>
>> On Thu, Jun 2, 2022 at 12:16 PM Alexey Romanenko <
>> aromanenko@gmail.com> wrote:
>>
>>> +1 That would be very helpful for mapping!
>>>
>>> On 2 Jun 2022, at 17:48, Ahmet Altay  wrote:
>>>
>>> Is it possible to add comments on the JIRAs with a link to the new
>>> corresponding github issue?
>>>
>>> On Thu, Jun 2, 2022 at 8:47 AM Danny McCormick <
>>> dannymccorm...@google.com> wrote:
>>>
 Thanks for the feedback, I agree it would be good to keep that
 option open - I updated the tool to write those to a file when we 
 create an
 issue. I'll share that after the migration.

 Thanks,
 Danny

 On Wed, Jun 1, 2022 at 7:03 PM Brian Hulette 
 wrote:

> Thanks Danny. Regarding links to GitHub issues, if we could at
> least save off a record of jira <-> issue mappings we could look at 
> adding
> the links later. I think it would be nice to have those links so that
> anyone landing in a jira through a search or an old link can quickly 
> find
> the current ticket, but I don't think that needs to block the 
> migration.
>
> On Wed, Jun 1, 2022 at 7:05 AM Danny McCormick <
> dannymccorm...@google.com> wrote:
>
>> Hey Brian,
>>
>> 1. Right now, the plan is to (1) turn on the issues tab, (2) make
>> the JIRA read only, (3) run the migration tool. Since the migration 
>> tool
>> won't be run until after Jiras are read only, there shouldn't be 
>> issues
>> with making sure everything gets captured.
>> 2. That current ordering does mean it's difficult to add a link
>> to the newly created Issue, and I hadn't built in that feature. With 
>> that
>> said, I will ask Infra if they're able to put up a banner redirecting
>> people to GitHub for the Beam project - that should hopefully 
>> minimize some
>> of the issues - and I'll also look into updating the tool to do that 
>> in
>> case the banner isn't doable. I'm also planning on doing a few 
>> passes to
>> update our 

Re: Failing beam_SeedJob

[Alexey Romanenko]

Thanks Valentyn, it may help! 

I’m wondering if the seed job was broken because of Pablo’s change or it just 
happened the same issue like in this thread and it was fixed just by Jenkins 
restart.

> On 3 Jun 2022, at 15:22, Valentyn Tymofieiev  wrote:
> 
> I am not aware of a straightforward way. I have been using this script: 
> https://gist.github.com/tvalentyn/08cdb2836d311c55ae6ec09a276aea2a 
>  
> +Pablo Estrada  investigated this in 
> https://issues.apache.org/jira/browse/BEAM-14377 
>  but Pablo's changes were 
> rolled back because somehow seed job became broken.
> 
> On Fri, Jun 3, 2022 at 2:56 PM Alexey Romanenko  > wrote:
> Yes, it’s ok now. 
> Thanks all!
> 
> Side question - is there a way to run a Jenkins job against specific PR? I 
> tried to specify different git refs as an input parameter but it didn’t work 
> for me…
> 
> —
> Alexey 
> 
>> On 3 Jun 2022, at 05:02, Ahmet Altay > > wrote:
>> 
>> Seed job looks healthy again: 
>> https://ci-beam.apache.org/job/beam_SeedJob/9762/ 
>>  .
>> 
>> On Thu, Jun 2, 2022 at 10:24 AM Ryan Thompson > > wrote:
>> I've filed a jira to infra and asked on the slack channel. Hopefully someone 
>> there has the power to restart the server.
>> 
>> https://issues.apache.org/jira/browse/INFRA-23335 
>> 
>> 
>> On Thu, Jun 2, 2022 at 12:41 PM Kenneth Knowles > > wrote:
>> Commented on the Jira. Seems like it happens somewhat rarely, but is 
>> sometimes resolved by a restart, and sometimes has to do with some version 
>> mismatch issues. I did not find anything like a real root cause, just 
>> trial-and-error fixes. I'm not certain what may have occurred around May 19 
>> to this infrastructure. Hoping INFRA can help us sort it out.
>> 
>> Kenn
>> 
>> On Thu, Jun 2, 2022 at 9:15 AM Alexey Romanenko > > wrote:
>> Thanks Ahmet and Ryan for taking a look!
>> 
>> I agree that referenced commits seems are not related, that us why I was 
>> puzzled with this.
>> 
>>> On 2 Jun 2022, at 17:56, Ahmet Altay >> > wrote:
>>> 
>>> 
>>> 
>>> On Thu, Jun 2, 2022 at 8:53 AM Ryan Thompson >> > wrote:
>>> I asked in the slack channel to restart jenkins. I'm looking through the 
>>> past messages to see if there's someone there I can tag.
>>> 
>>> Thank you. Unfortunately, I do not believe we have a single expert we can 
>>> tag.
>>>  
>>> Am I right in understanding this service is managed by someone in apache 
>>> and not us?
>>> 
>>> It is mixed. ASF Infra works with a vendor and they run a hosted jenkins 
>>> instance. We control the configuration of the instance, and the worker 
>>> nodes.
>>>  
>>> 
>>> On Thu, Jun 2, 2022 at 11:47 AM Ahmet Altay >> > wrote:
>>> /cc @Kenneth Knowles 
>>> On Thu, Jun 2, 2022 at 8:44 AM Ahmet Altay >> > wrote:
>>> I do not have a great idea but googling about the error, similar errors 
>>> were resolved by restarting jenkins. We could try that. We may need to ask 
>>> infra. ( @Ryan Thompson  - could you please 
>>> infra to restart jenkins?)
>>> 
>>> I do not think this issue is related to any change in the source control. 
>>> The commit referenced in the first failed job is an unrelated doc change. 
>>> 
>>> 
>>> On Thu, Jun 2, 2022 at 7:57 AM Alexey Romanenko >> > wrote:
>>> I created a jira for this (not sure if it’s P0, but P1 for sure):
>>> https://issues.apache.org/jira/browse/BEAM-14548 
>>> 
>>> 
>>> Could someone, who has more knowledge than me in Beam 
>>> infrastructure/Jenkins, take a look, please?
>>> 
>>> —
>>> Alexey
>>> 
 On 31 May 2022, at 17:08, Alexey Romanenko >>> > wrote:
 
 The first failed job is https://ci-beam.apache.org/job/beam_SeedJob/9696/ 
 
 It fails with this error (that says not so much):
 
 Processing DSL script .test-infra/jenkins/job_00_seed.groovy
 Processing DSL script 
 .test-infra/jenkins/job_CancelStaleDataflowJobs.groovy
 Processing DSL script 
 .test-infra/jenkins/job_CleanUpPrebuiltSDKImages.groovy
 Processing DSL script .test-infra/jenkins/job_Dependency_Check.groovy
 ERROR: java.io.IOException: Failed to persist config.xml
 
  and I don’t see any recent changes for these files.
 
> On 31 May 2022, at 16:24, Alexey Romanenko  > wrote:
> 
> Hi everyone,
> 
> Jenkins 

Re: Jira -> GitHub Issues Migration (This Friday)

[Hector Miuler Malpica Gallegos]

When will github issues be enabled?  I understood that it would be today



*Hector Miuler Malpica Gallegos *



El jue, 2 jun 2022 a la(s) 21:35, Hector Miuler Malpica Gallegos (
miu...@gmail.com) escribió:

>
> hahaha!!! excuse me, I'm thinking in the flink project when read the last
> email, I do not know why.
>
>
> *Hector Miuler Malpica Gallegos *
>
>
>
> El jue, 2 jun 2022 a la(s) 18:04, Danny McCormick (
> dannymccorm...@google.com) escribió:
>
>> Thanks for calling that out Hector - the migration will only migrate
>> issues from the Beam project (that one is from the Flink project), so I
>> don't think it should be an issue.
>>
>> Thanks,
>> Danny
>>
>> On Thu, Jun 2, 2022 at 6:38 PM Hector Miuler Malpica Gallegos <
>> miu...@gmail.com> wrote:
>>
>>> This migration includes the issues of the component `Kubernetes
>>> Operator` ? like this issue FLINK-27820
>>>  ? this issues
>>> correspond to the repository
>>> https://github.com/apache/flink-kubernetes-operator, keep it in mind.
>>>
>>>
>>> *Hector Miuler Malpica Gallegos *
>>>
>>>
>>>
>>> El jue, 2 jun 2022 a la(s) 12:33, Danny McCormick (
>>> dannymccorm...@google.com) escribió:
>>>
 Given the consensus here, I updated the tool to do this. This means
 that we won't update the JIRAs to be read-only until after the migration is
 complete. I'll rerun the tool if any extra jiras come in during the
 intervening period. The tool will also still write the mapping to the file
 in case there are unforeseen issues so that we can backfill if needed.

 Thanks for the suggestion and followup Brian, Ahmet, and Alexey.

 On Thu, Jun 2, 2022 at 12:16 PM Alexey Romanenko <
 aromanenko@gmail.com> wrote:

> +1 That would be very helpful for mapping!
>
> On 2 Jun 2022, at 17:48, Ahmet Altay  wrote:
>
> Is it possible to add comments on the JIRAs with a link to the new
> corresponding github issue?
>
> On Thu, Jun 2, 2022 at 8:47 AM Danny McCormick <
> dannymccorm...@google.com> wrote:
>
>> Thanks for the feedback, I agree it would be good to keep that option
>> open - I updated the tool to write those to a file when we create an 
>> issue.
>> I'll share that after the migration.
>>
>> Thanks,
>> Danny
>>
>> On Wed, Jun 1, 2022 at 7:03 PM Brian Hulette 
>> wrote:
>>
>>> Thanks Danny. Regarding links to GitHub issues, if we could at least
>>> save off a record of jira <-> issue mappings we could look at adding the
>>> links later. I think it would be nice to have those links so that anyone
>>> landing in a jira through a search or an old link can quickly find the
>>> current ticket, but I don't think that needs to block the migration.
>>>
>>> On Wed, Jun 1, 2022 at 7:05 AM Danny McCormick <
>>> dannymccorm...@google.com> wrote:
>>>
 Hey Brian,

 1. Right now, the plan is to (1) turn on the issues tab, (2) make
 the JIRA read only, (3) run the migration tool. Since the migration 
 tool
 won't be run until after Jiras are read only, there shouldn't be issues
 with making sure everything gets captured.
 2. That current ordering does mean it's difficult to add a link to
 the newly created Issue, and I hadn't built in that feature. With that
 said, I will ask Infra if they're able to put up a banner redirecting
 people to GitHub for the Beam project - that should hopefully minimize 
 some
 of the issues - and I'll also look into updating the tool to do that in
 case the banner isn't doable. I'm also planning on doing a few passes 
 to
 update our docs and code comments from Jiras to issues once the 
 migration
 is done.

 Thanks,
 Danny

 On Tue, May 31, 2022 at 8:09 PM Brian Hulette 
 wrote:

> Thanks Danny, it's great to see this happening!
>
> A couple of questions:
> - Is there something we can do to remind people creating a jira
> that they should create a bug instead (e.g. a template)? If not I 
> suppose
> we can just re-run the migration tool a few times up until jira 
> creation is
> disabled to make sure everything is captured.
> - Will your migration tooling comment on the original jira with a
> link to the new issue in GitHub?
>
> Brian
>
> On Tue, May 31, 2022 at 9:57 AM Robert Bradshaw <
> rober...@google.com> wrote:
>
>> Thanks for finally making this happen.
>>
>> On Tue, May 31, 2022 at 7:18 AM Sachin Agarwal <
>> sachi...@google.com> wrote:
>> >
>> > Thank you Danny! This will help us a lot, 

Re: Failing beam_SeedJob

[Alexey Romanenko]

Yes, it’s ok now. 
Thanks all!

Side question - is there a way to run a Jenkins job against specific PR? I 
tried to specify different git refs as an input parameter but it didn’t work 
for me…

—
Alexey 

> On 3 Jun 2022, at 05:02, Ahmet Altay  wrote:
> 
> Seed job looks healthy again: 
> https://ci-beam.apache.org/job/beam_SeedJob/9762/ 
>  .
> 
> On Thu, Jun 2, 2022 at 10:24 AM Ryan Thompson  > wrote:
> I've filed a jira to infra and asked on the slack channel. Hopefully someone 
> there has the power to restart the server.
> 
> https://issues.apache.org/jira/browse/INFRA-23335 
> 
> 
> On Thu, Jun 2, 2022 at 12:41 PM Kenneth Knowles  > wrote:
> Commented on the Jira. Seems like it happens somewhat rarely, but is 
> sometimes resolved by a restart, and sometimes has to do with some version 
> mismatch issues. I did not find anything like a real root cause, just 
> trial-and-error fixes. I'm not certain what may have occurred around May 19 
> to this infrastructure. Hoping INFRA can help us sort it out.
> 
> Kenn
> 
> On Thu, Jun 2, 2022 at 9:15 AM Alexey Romanenko  > wrote:
> Thanks Ahmet and Ryan for taking a look!
> 
> I agree that referenced commits seems are not related, that us why I was 
> puzzled with this.
> 
>> On 2 Jun 2022, at 17:56, Ahmet Altay > > wrote:
>> 
>> 
>> 
>> On Thu, Jun 2, 2022 at 8:53 AM Ryan Thompson > > wrote:
>> I asked in the slack channel to restart jenkins. I'm looking through the 
>> past messages to see if there's someone there I can tag.
>> 
>> Thank you. Unfortunately, I do not believe we have a single expert we can 
>> tag.
>>  
>> Am I right in understanding this service is managed by someone in apache and 
>> not us?
>> 
>> It is mixed. ASF Infra works with a vendor and they run a hosted jenkins 
>> instance. We control the configuration of the instance, and the worker nodes.
>>  
>> 
>> On Thu, Jun 2, 2022 at 11:47 AM Ahmet Altay > > wrote:
>> /cc @Kenneth Knowles 
>> On Thu, Jun 2, 2022 at 8:44 AM Ahmet Altay > > wrote:
>> I do not have a great idea but googling about the error, similar errors were 
>> resolved by restarting jenkins. We could try that. We may need to ask infra. 
>> ( @Ryan Thompson  - could you please infra 
>> to restart jenkins?)
>> 
>> I do not think this issue is related to any change in the source control. 
>> The commit referenced in the first failed job is an unrelated doc change. 
>> 
>> 
>> On Thu, Jun 2, 2022 at 7:57 AM Alexey Romanenko > > wrote:
>> I created a jira for this (not sure if it’s P0, but P1 for sure):
>> https://issues.apache.org/jira/browse/BEAM-14548 
>> 
>> 
>> Could someone, who has more knowledge than me in Beam 
>> infrastructure/Jenkins, take a look, please?
>> 
>> —
>> Alexey
>> 
>>> On 31 May 2022, at 17:08, Alexey Romanenko >> > wrote:
>>> 
>>> The first failed job is https://ci-beam.apache.org/job/beam_SeedJob/9696/ 
>>> 
>>> It fails with this error (that says not so much):
>>> 
>>> Processing DSL script .test-infra/jenkins/job_00_seed.groovy
>>> Processing DSL script .test-infra/jenkins/job_CancelStaleDataflowJobs.groovy
>>> Processing DSL script 
>>> .test-infra/jenkins/job_CleanUpPrebuiltSDKImages.groovy
>>> Processing DSL script .test-infra/jenkins/job_Dependency_Check.groovy
>>> ERROR: java.io.IOException: Failed to persist config.xml
>>> 
>>>  and I don’t see any recent changes for these files.
>>> 
 On 31 May 2022, at 16:24, Alexey Romanenko >>> > wrote:
 
 Hi everyone,
 
 Jenkins job `beam_SeedJob` keeps failing starting from May 19th. The last 
 successful build [2] was 12 days ago.
 Does anyone know the reasons of this?
 
 —
 Alexey
 
 
 [1] https://ci-beam.apache.org/job/beam_SeedJob/ 
 
 [2] https://ci-beam.apache.org/job/beam_SeedJob/lastSuccessfulBuild/ 
 

 
>>> 
>> 
>