Flaky test issue report (59)

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

P1 issues report (77)

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

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

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

Re: Failing beam_SeedJob

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

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

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

Re: Failing beam_SeedJob

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: >