Re: Beam snapshots broken

Thank you for fixing this, Scott. I also can confirm that it works for me now. > On 2 Jan 2019, at 22:36, Ismaël Mejía wrote: > > Thanks Scott, I just tested and the errors I found are fixed and > everything seems to work now. Snapshots are being correctly updated > too. > > On Wed, Jan 2, 2019

Re: Beam snapshots broken

Thanks Scott, I just tested and the errors I found are fixed and everything seems to work now. Snapshots are being correctly updated too. On Wed, Jan 2, 2019 at 6:19 PM Scott Wegner wrote: > > Yes, I believe this will be fixed with the vendoring release. > > I am back from the holidays now and re

Re: Beam snapshots broken

Yes, I believe this will be fixed with the vendoring release. I am back from the holidays now and ready to pick this up. On Thu, Dec 27, 2018 at 10:56 AM Ismaël Mejía wrote: > Thanks Andrew for the info. > I think things can wait a bit considering the time of the year, I just > wanted to raise

Re: Beam snapshots broken

Thanks Andrew for the info. I think things can wait a bit considering the time of the year, I just wanted to raise awareness about the issue. I suppose that we can wait, it should not be long before the vendoring release is done and this will fix this if I understood correctly. If anyone else is bl

Re: Beam snapshots broken

https://issues.apache.org/jira/browse/BEAM-6282 Kenn (and everyone else who has context on this change) are out this week, so I don't think anyone is making progress on it. Is this something that can wait a week or two? If not we should revert https://github.com/apache/beam/pull/7324 Andrew On T

Re: Beam snapshots broken

I can reproduce this on my machine, and reverting https://github.com/apache/beam/pull/7324 fixed the problem. There is a separate thread in dev@ about releasing vendored gRPC v0.2, I'm wondering if it will this issue. On Thu, Dec 27, 2018 at 5:20 PM Ismaël Mejía wrote: > Looks like snapshots are

Re: Beam snapshots broken

Looks like snapshots are broken again since 20 december, can somebody PTAL? Seems like some part of the vendoring could be related to this failure (maybe it is looking for the unpublished version)? Running some tests in one existing application I found this [ERROR] Tests run: 1, Failures: 0, Error

Re: Beam snapshots broken

Looks like the recent failure (like this job ) is related to ':beam-sdks-python:test' change introduced in this PR . `./gradlew :beam-sdk

Re: Beam snapshots broken

Beam9 is offline right now. But, the job also failed on beam4 and 13 with "Could not determine the dependencies of task ':beam-sdks-python:test.". Seems like the task dependency did not setup properly. On Wed, Dec 12, 2018 at 2:03 AM Ismaël Mejía wrote: > You are right it seems that it was rel

Re: Beam snapshots broken

You are right it seems that it was related to beam9 (wondering if it was bad luck that it was always assigned to beam9 or we can improve that poor balancing error). However it failed again today against beam13 maybe this time is just a build issue but seems related to python too. On Tue, Dec 11, 2

Beam snapshots broken

It seems that Beam snapshots are broken since Dec. 2 https://builds.apache.org/view/A-D/view/Beam/job/beam_Release_Gradle_NightlySnapshot/ It seems "The :beam-website:startDockerContainer task failed." Can somebody please take a look.