Build failed in Jenkins: beam_SeedJob #1607

See -- GitHub pull request #5218 of commit 71cdb8f168bea0b1cb45822450dadf7380e08b5a, no merge conflicts. Setting status of 71cdb8f168bea0b1cb45822450dadf7380e08b5a to PENDING with url

Re: [SQL] Reconciling Beam SQL Environments with Calcite Schema

I'm just starting to move forward on this. Looking at my team's short term needs for SQL, option one would be good enough, however I agree with Kenn that we want something like option two eventually. I also don't want to break existing users and it sounds like there is at least one custom

Jenkins build is back to normal : beam_SeedJob #1611

See

Jenkins build is back to normal : beam_SeedJob #1609

See

Build failed in Jenkins: beam_SeedJob #1610

See -- GitHub pull request #5218 of commit 614d205083bbb5a2123977a74b57a48fff177979, no merge conflicts. Setting status of 614d205083bbb5a2123977a74b57a48fff177979 to PENDING with url

Java compiler OOMs on Jenkins/Gradle

Hi, I've seen the same issue twice in a row on PR https://github.com/apache/beam/pull/4264 : the Java precommit fails with messages like: > Task :beam-sdks-java-core:compileTestJava An exception has occurred in the compiler ((version info not available)). Please file a bug against the Java

Re: Java compiler OOMs on Jenkins/Gradle

Thanks! FWIW seems that my other Jenkins build is about to fail with the same issue https://builds.apache.org/job/beam_PreCommit_Java_GradleBuild/4806/ - "Expiring Daemon because JVM Tenured space is exhausted" On Tue, May 1, 2018 at 1:36 PM Lukasz Cwik wrote: >

Re: Java compiler OOMs on Jenkins/Gradle

+sweg...@google.com who is currently messing around with tuning some Gradle flags related to the JVM and its memory usage. On Tue, May 1, 2018 at 1:34 PM Eugene Kirpichov wrote: > Hi, > > I've seen the same issue twice in a row on PR >

Re: Java compiler OOMs on Jenkins/Gradle

Sorry about the instability. We need to get the Gradle jobs tuned for our Jenkins machines, and there's no way to test my configuration changes without affecting all jobs :-/ The changes I'm making are here: https://github.com/apache/beam/pull/5218 It seems that they're still not quite right:

Build failed in Jenkins: beam_SeedJob #1608

See -- GitHub pull request #5218 of commit 1f36f495690b868ccc63d6f0898cfb49847e68cf, no merge conflicts. Setting status of 1f36f495690b868ccc63d6f0898cfb49847e68cf to PENDING with url

Re: Gradle Status: Migrated!

Luke did gather data which showed that on our Jenkins executors the Gradle build was much faster than the Maven build. Also right now we have incremental builds turned off, but once we're confident enough to enable them (at least for local development) that will often drop build times a lot. On

Re: Gradle Status: Migrated!

Thanks, for me, Maven 3.5.2 takes quite the same time than Gradle (using the wrapper). It's maybe related to my environment. Anyway, I'm doing a complete build review both in term of building time, and equivalence (artifacts publishing, test, plugin execution). I will provide an update soon.

Re: Kafka connector for Beam Python SDK

Thanks all for the comments. Based on the discussion so far, looks like we have to flesh out the cross-language transforms feature quite a bit before we can utilize some of the existing Java IO in other SDKs. This might involve redesigning some of the existing Java IOs to allow expressing second

Build failed in Jenkins: beam_Release_Gradle_NightlySnapshot #25

See Changes: [ankurgoenka] fixing generic errors [echauchot] [BEAM-3119] ensure metrics thread is shutdown [echauchot] [BEAM-4088] Rebase on master, fix conflicts and adapt test to master

Re: Gradle Status: Migrated!

Hi Scott While https://issues.apache.org/jira/plugins/servlet/mobile#issue/BEAM-4057 is open, gradle is a concurrent of maven but maven must stay the default build tool cause gradle breaks users. Le 1 mai 2018 01:59, "Scott Wegner" a écrit : > Many many of you have been

Re: Gradle Status: Migrated!

By the way, I'm curious: did someone evaluate the build time gap between Maven and Gradle ? One of the main reason to migrate to Gradle was the inc build and build time. The builds I have launched are quite the same in duration. I will do deeper tests to evaluate the gap. Regards JB On

Re: Gradle Status: Migrated!

Hi Scott, thanks for the update! Just a clarification about IO performance tests: those were fully migrated in Beam and all task necessary for running them are there but Jenkins jobs still run mvn commands. This is due the fact that PerfkitBenchmarker code (which is invoked by Jenkins and

Re: Gradle Status: Migrated!

Raw execution time for tasks from clean is not the only thing to test. I would say it is not even important. Try these from clean: - Gradle: ./gradlew :beam-sdks-java-io-mongodb:test && ./gradlew : beam-sdks-java-io-mongodb:test - Maven: mvn -pl sdks/java/io/mongodb test -am && mvn -pl

Re: Gradle Status: Migrated!

Thanks for the update Kenn, that makes sense. I'm checking the artifacts generated by Gradle right now. Regards JB On 01/05/2018 17:42, Kenneth Knowles wrote: Raw execution time for tasks from clean is not the only thing to test. I would say it is not even important. Try these from clean:  

Re: [PROPOSAL] Preparing 2.5.0 release next week

Sounds good, thanks J.B. Feel free to ping if you need anything. On Mon, Apr 30, 2018 at 10:12 PM Jean-Baptiste Onofré wrote: > That's a good idea ! I think using Slack to ping/ask is a good way as it's > async. > > Regards > JB > > On 05/01/2018 06:51 AM, Reuven Lax wrote: >

Re: Gradle Status: Migrated!

JB - for your comparison, please also omit cross-compiling all the Go examples because they are only built using Gradle. On Tue, May 1, 2018 at 8:59 AM Jean-Baptiste Onofré wrote: > Thanks for the update Kenn, that makes sense. > > I'm checking the artifacts generated by