Re: Broken seed job

2018-07-10 Thread Łukasz Gajowy
I didn't edit the "Standalone Seed job", only the "SeedJob". Now every time someone tries to run the seed job ("Run seed job") it results in an error even despite prior running the standalone job from master branch the way you described. śr., 11 lip 2018 o 01:25 Lukasz Cwik napisał(a): >

Build failed in Jenkins: beam_SeedJob #2193

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit d647a14cb3aa72e3b21e5a94f1430b00245a84b2, no merge conflicts. Setting status of d647a14cb3aa72e3b21e5a94f1430b00245a84b2 to PENDING with url

Re: Broken seed job

2018-07-10 Thread Lukasz Cwik
job_seed_standalone should only be edited when we know that the regular seed job is in a healthy state. Note, that you can always recover back to what is checked in master by: 1) Creating an empty PR 2) Using the standalone seed job trigger phrase: "Run Standalone Seed Job" I kicked one off

Broken seed job

2018-07-10 Thread Łukasz Gajowy
Hi, while working on Jenkins' seed job, some changes I introduced didn't get reverted even after running the seed job again from the master branch. This is why seed job is now failing. More details here [1] and here [2]. Since I can operate only with jobs phrase-triggered from GitHub's PR, I

Build failed in Jenkins: beam_SeedJob #2192

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit a0969743a826820d58fc7558a44fce0d4ee859a0, no merge conflicts. Setting status of a0969743a826820d58fc7558a44fce0d4ee859a0 to PENDING with url

[PROPOSAL] JIRA Automation for Beam Dependency Upgrades

2018-07-10 Thread Yifan Zou
Hi all, I have a short proposal on automatically file JIRA tickets that tracks the Beam dependency update process. Any comments are welcome. https://docs.google.com/document/d/1XXTMnofizSQZSorZy4NFlxKfx5f17PGRmws-DngoTms/edit# Regards. Yifan

Build failed in Jenkins: beam_SeedJob #2191

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5920 of commit 4715449665ae235f96c7a67ce5f80b774d5474e5, no merge conflicts. Setting status of 4715449665ae235f96c7a67ce5f80b774d5474e5 to PENDING with url

Vendoring / Shading Protobuf and gRPC

2018-07-10 Thread Lukasz Cwik
With the merge of PR #5594[1], we started shading all gRPC / Protobuf dependencies within all the modules that depended on the model/* dependencies by vendoring them. The vendored versions are built and packaged into the model jars (they should be separated out once I figure out how to generate

Re: CODEOWNERS for apache/beam repo

2018-07-10 Thread Udi Meiri
Robert, the docs say: "The people you choose as code owners must have write permissions for the repository," but I want to ignore that for now and see what happens. :) Also, I'm not sure how the auto-assignment works. Does it round-robin? Will

Build failed in Jenkins: beam_SeedJob #2190

2018-07-10 Thread Apache Jenkins Server
See Changes: [Pablo] Improving signing of all published artifacts and adding test publication [Pablo] Removing extra publication [cclauss] [BEAM-3761] Define cmp() in Python 3 [cclauss] [BEAM-3959] Add Python 3

Re: drop nexmark perfkit tables

2018-07-10 Thread Etienne Chauchot
Thanks Andrew !Le mardi 10 juillet 2018 à 09:11 -0700, Andrew Pilloud a écrit : > Done. The UI doesn't make it easy to drop the tables without dropping the > dataset. In case it needs to be done again, > here is what I ran: > for table in $(bq ls -a --dataset_id apache-beam-testing:nexmark | awk

Re: CODEOWNERS for apache/beam repo

2018-07-10 Thread Ahmet Altay
+1 I added my name and a few others names that frequently do reviews in some areas. On Tue, Jul 10, 2018 at 10:23 AM, Jean-Baptiste Onofré wrote: > +1 > > I added my name on some components ;) > > Thanks ! > Regards > JB > > On 10/07/2018 02:06, Udi Meiri wrote: > > Hi everyone, > > > > I'm

Re: CODEOWNERS for apache/beam repo

2018-07-10 Thread Rafael Fernandez
+1! On Tue, Jul 10, 2018 at 8:51 AM Robert Burke wrote: > +1 > If non-committers are welcome in the file, I'm happy to assist Henning > with Go SDK reviews.(@lostluck) > > > On Tue, Jul 10, 2018, 8:47 AM Alexey Romanenko > wrote: > >> +1, >> Udi, thank you for taking care of this! >> I added

Re: drop nexmark perfkit tables

2018-07-10 Thread Andrew Pilloud
Done. The UI doesn't make it easy to drop the tables without dropping the dataset. In case it needs to be done again, here is what I ran: for table in $(bq ls -a --dataset_id apache-beam-testing:nexmark | awk 'NR > 2 {print $1}'); do bq rm -f apache-beam-testing:nexmark.$table; done Andrew On

Build failed in Jenkins: beam_SeedJob #2189

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit a0969743a826820d58fc7558a44fce0d4ee859a0, no merge conflicts. Setting status of a0969743a826820d58fc7558a44fce0d4ee859a0 to PENDING with url

Re: CODEOWNERS for apache/beam repo

2018-07-10 Thread Robert Burke
+1 If non-committers are welcome in the file, I'm happy to assist Henning with Go SDK reviews.(@lostluck) On Tue, Jul 10, 2018, 8:47 AM Alexey Romanenko wrote: > +1, > Udi, thank you for taking care of this! > I added myself as a reviewer of some IO components. > > > On 10 Jul 2018, at 17:00,

Re: CODEOWNERS for apache/beam repo

2018-07-10 Thread Alexey Romanenko
+1, Udi, thank you for taking care of this! I added myself as a reviewer of some IO components. > On 10 Jul 2018, at 17:00, Henning Rohde wrote: > > +1. Sounds like a useful improvement. > > Udi -- do the reviewers in this file need to be committers for the PR > auto-assignment to work? >

[metrics] inside the (not portable) runner

2018-07-10 Thread Etienne Chauchot
Guys, I recently had the occasion to make a diagram to explain to a user the architecture of metrics inside the runner in the not-portable world (for now). I think I will use it for my upcoming talk at the ApacheCon. I wanted to share it with you as a piece of documentation and also for

Build failed in Jenkins: beam_SeedJob #2188

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit a0969743a826820d58fc7558a44fce0d4ee859a0, no merge conflicts. Setting status of a0969743a826820d58fc7558a44fce0d4ee859a0 to PENDING with url

Build failed in Jenkins: beam_SeedJob #2187

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit a0969743a826820d58fc7558a44fce0d4ee859a0, no merge conflicts. Setting status of a0969743a826820d58fc7558a44fce0d4ee859a0 to PENDING with url

Build failed in Jenkins: beam_SeedJob #2186

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit a0969743a826820d58fc7558a44fce0d4ee859a0, no merge conflicts. Setting status of a0969743a826820d58fc7558a44fce0d4ee859a0 to PENDING with url

Build failed in Jenkins: beam_SeedJob #2185

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit a0969743a826820d58fc7558a44fce0d4ee859a0, no merge conflicts. Setting status of a0969743a826820d58fc7558a44fce0d4ee859a0 to PENDING with url

Build failed in Jenkins: beam_SeedJob #2184

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit a0969743a826820d58fc7558a44fce0d4ee859a0, no merge conflicts. Setting status of a0969743a826820d58fc7558a44fce0d4ee859a0 to PENDING with url

Build failed in Jenkins: beam_SeedJob #2183

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5915 of commit 71ccdaa868e75409e9298dc8aef303022d7cd2c5, no merge conflicts. Setting status of 71ccdaa868e75409e9298dc8aef303022d7cd2c5 to PENDING with url

drop nexmark perfkit tables

2018-07-10 Thread Etienne Chauchot
Hi Guys, Can anyone who has the rights (PMC members maybe) drop all the BigQuery tables from project `apache-beam-testing` in the dataset `nexmark`, they contain incorrect data. Please do not drop the nexmark dataset, only the tables. Don't worry the tables will be re-created with next commit

Re: CODEOWNERS for apache/beam repo

2018-07-10 Thread Henning Rohde
+1. Sounds like a useful improvement. Udi -- do the reviewers in this file need to be committers for the PR auto-assignment to work? On Tue, Jul 10, 2018 at 1:59 AM Łukasz Gajowy wrote: > +1. It will certainly be useful. I added myself (and a fellow contributor) > to some components (IO

Build failed in Jenkins: beam_SeedJob #2181

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5915 of commit 71ccdaa868e75409e9298dc8aef303022d7cd2c5, no merge conflicts. Setting status of 71ccdaa868e75409e9298dc8aef303022d7cd2c5 to PENDING with url

Build failed in Jenkins: beam_SeedJob #2180

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5915 of commit 084ebd2dc33d148b91d6199c3faa7a53d80c7f2b, no merge conflicts. Setting status of 084ebd2dc33d148b91d6199c3faa7a53d80c7f2b to PENDING with url

Build failed in Jenkins: beam_SeedJob #2179

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5915 of commit 084ebd2dc33d148b91d6199c3faa7a53d80c7f2b, no merge conflicts. Setting status of 084ebd2dc33d148b91d6199c3faa7a53d80c7f2b to PENDING with url

Build failed in Jenkins: beam_SeedJob #2178

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5915 of commit 4671da6f82963aff97d160a6fa01e52dddb1ba78, no merge conflicts. Setting status of 4671da6f82963aff97d160a6fa01e52dddb1ba78 to PENDING with url

Jenkins build is back to normal : beam_SeedJob #2176

2018-07-10 Thread Apache Jenkins Server
See

Build failed in Jenkins: beam_SeedJob #2175

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5915 of commit aaa985e681a519b9dc6723d253769f7142c231ed, no merge conflicts. Setting status of aaa985e681a519b9dc6723d253769f7142c231ed to PENDING with url

Build failed in Jenkins: beam_SeedJob #2174

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit a0969743a826820d58fc7558a44fce0d4ee859a0, no merge conflicts. Setting status of a0969743a826820d58fc7558a44fce0d4ee859a0 to PENDING with url

Build failed in Jenkins: beam_SeedJob #2173

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5914 of commit 5f4a205fcffbb0b154406e5d95d56a32ca9bac70, no merge conflicts. Setting status of 5f4a205fcffbb0b154406e5d95d56a32ca9bac70 to PENDING with url

Build failed in Jenkins: beam_SeedJob #2172

2018-07-10 Thread Apache Jenkins Server
See -- GitHub pull request #5913 of commit f68c0243c394e2c8fc808dec7f471f21b303c09b, no merge conflicts. Setting status of f68c0243c394e2c8fc808dec7f471f21b303c09b to PENDING with url

Re: Performance issue in Beam 2.4 onwards

2018-07-10 Thread Reuven Lax
If we added something slow to the core library in order to better test DirectRunner, that does sound like an unfortunate bug. On Mon, Jul 9, 2018 at 11:21 PM Vojtech Janota wrote: > Hi guys, > > Thank you for all of your feedback. I have created relevant issue in JIRA: >

Re: CODEOWNERS for apache/beam repo

2018-07-10 Thread Łukasz Gajowy
+1. It will certainly be useful. I added myself (and a fellow contributor) to some components (IO testing related mostly). Thanks, Łukasz wt., 10 lip 2018 o 02:06 Udi Meiri napisał(a): > Hi everyone, > > I'm proposing to add auto-reviewer-assignment using Github's CODEOWNERS > mechanism. >

Re: Performance issue in Beam 2.4 onwards

2018-07-10 Thread Vojtech Janota
Hi guys, Thank you for all of your feedback. I have created relevant issue in JIRA: https://issues.apache.org/jira/browse/BEAM-4750 @Lukasz: me mentioning the DirectRunner was somewhat unfortunate - the bottleneck was introduced into the core library and so Flink and Spark runners would be