Re: What to do about issues that track flaky tests?

2022-09-14 Thread Manu Zhang
Agreed. I also mentioned in a previous email that some issues have been open for a long time (before being migrated to GitHub) and it's possible that those tests can pass constantly now. We may double check and close them since reopening is just one click. Manu On Thu, Sep 15, 2022 at 6:58 AM

Re: [PROPOSAL] Preparing for 2.42.0 Release

2022-09-14 Thread Robert Burke
I'm feeling much better. Cherry picks have quieted down, so I'll be working on an RC0 tomorrow. Your friendly neighborhood release manager Robert Burke On Thu, Sep 8, 2022, 3:01 PM Robert Burke wrote: > My recent travels appear to prevent me from working at my best and focus > on getting the

Re: What to do about issues that track flaky tests?

2022-09-14 Thread Austin Bennett
+1 to being realistic -- proper labels are worthwhile. Though, some flaky tests probably should be P1, and just because isn't addressed in a timely manner doesn't mean it isn't a P1 - though, it does mean it wasn't addressed. On Wed, Sep 14, 2022 at 1:19 PM Kenneth Knowles wrote: > I would

What to do about issues that track flaky tests?

2022-09-14 Thread Kenneth Knowles
I would like to make this alert email actionable. I went through most of these issues. About half are P1 "flake" issues. I don't think magically expecting them to be deflaked is helpful. So I have a couple ideas: 1. Exclude "flake" P1s from this email. This is what we used to do. But then... are

Beam Community Meetup

2022-09-14 Thread hello
Join the next Beam Community Meetup! Beam Community Meetup Thursday Sep 22, 2022 ⋅ 11:30am – 12:30pm Central Time - Mexico City Location https://www.crowdcast.io/e/beam-community-meetup

Re: [Infrastructure] Periodically run Java microbenchmarks on Jenkins

2022-09-14 Thread Alexey Romanenko
Ahh, great! I didn’t know that 'beam-perf’ label is used for that. Thanks! > On 14 Sep 2022, at 17:47, Andrew Pilloud wrote: > > We do have a dedicated machine for benchmarks. This is a single > machine limited to running one test at a time. Set the > jenkinsExecutorLabel for the job to

Re: (Golang)HOW TO WRITE BIGQUERY TABLE USING SUSCRIBE TO PUBSUB MESSAGE.THROUGH APACHE BEAM IN GOLANG.

2022-09-14 Thread Ritesh Ghorse via dev
Hi, The bigqueryio.Write() infers a schema type from the PCollection you are writing. In the code, you are directly writing the output of pubsubio.Read which is of []byte. You need to do insert a ParDo that would decode and convert it to schema (Schema in go SDK is just a struct with exported

Re: [Infrastructure] Periodically run Java microbenchmarks on Jenkins

2022-09-14 Thread Andrew Pilloud
We do have a dedicated machine for benchmarks. This is a single machine limited to running one test at a time. Set the jenkinsExecutorLabel for the job to 'beam-perf' to use it. For example:

Re: (Golang)HOW TO WRITE BIGQUERY TABLE USING SUSCRIBE TO PUBSUB MESSAGE.THROUGH APACHE BEAM IN GOLANG.

2022-09-14 Thread Abyakta Bal
*correcting this:-* *i am using this code: to read from pubsub message* col := pubsubio.Read(s, project, *input, {Subscription: sub.ID()}) *i am using this code:- write in bigquery* bigqueryio.Write(s, project, *output,*col)* On Wed, Sep 14, 2022 at 6:39 PM Abyakta Bal wrote: > Dear Team, > i

(Golang)HOW TO WRITE BIGQUERY TABLE USING SUSCRIBE TO PUBSUB MESSAGE.THROUGH APACHE BEAM IN GOLANG.

2022-09-14 Thread Abyakta Bal
Dear Team, i am trying to write bigquery table using pubsub message pull/suscribe .So i am unable to convert *beam.collection []uint8/bytes* to *beam.collection* *schema type in go apachebeamsdk.*i am facing this issue :-*schema type must be struct: []uint8* *i am using this code: to read from

Re: [Infrastructure] Periodically run Java microbenchmarks on Jenkins

2022-09-14 Thread Alexey Romanenko
I think it depends on the goal why to run that benchmarks. In ideal case, we need to run them on the same dedicated machine(s) and with the same configuration all the time but I’m not sure that it can be achieved in current infrastructure reality. On the other hand, IIRC, the initial goal of

Beam High Priority Issue Report (54)

2022-09-14 Thread beamactions
This is your daily summary of Beam's current high priority issues that may need attention. See https://beam.apache.org/contribute/issue-priorities for the meaning and expectations around issue priorities. Unassigned P1 Issues: https://github.com/apache/beam/issues/23227 [Bug]: Python SDK