Re: beam_PreCommit_Go_MavenInstall appears perma-red

[Henning Rohde]

Ah. It looks like an issue with pulling dependencies. There is a followup
PR that might address it: https://github.com/apache/beam/pull/4633. Sorry
for the noise.

On Mon, Feb 12, 2018 at 9:48 AM, Kenneth Knowles  wrote:

> Oh, yes. Copy/paste fail. I mean the gradle one.
>
> On Mon, Feb 12, 2018 at 9:46 AM, Henning Rohde  wrote:
>
>> Let me take a look. I was not aware there was a regression with the Maven
>> Go precommit (or do you mean the Gradle one?).
>>
>> Henning
>>
>> On Mon, Feb 12, 2018 at 8:59 AM, Kenneth Knowles  wrote:
>>
>>> Does anyone have context on the status here? I know it is a new build.
>>> Perhaps it can be comment-triggered only until it is reliable enough that
>>> we would be willing to block merges on it?
>>>
>>> Kenn
>>>
>>
>>
>

Re: beam_PreCommit_Go_MavenInstall appears perma-red

[Kenneth Knowles]

Oh, yes. Copy/paste fail. I mean the gradle one.

On Mon, Feb 12, 2018 at 9:46 AM, Henning Rohde  wrote:

> Let me take a look. I was not aware there was a regression with the Maven
> Go precommit (or do you mean the Gradle one?).
>
> Henning
>
> On Mon, Feb 12, 2018 at 8:59 AM, Kenneth Knowles  wrote:
>
>> Does anyone have context on the status here? I know it is a new build.
>> Perhaps it can be comment-triggered only until it is reliable enough that
>> we would be willing to block merges on it?
>>
>> Kenn
>>
>
>

Re: beam_PreCommit_Go_MavenInstall appears perma-red

[Henning Rohde]

Let me take a look. I was not aware there was a regression with the Maven
Go precommit (or do you mean the Gradle one?).

Henning

On Mon, Feb 12, 2018 at 8:59 AM, Kenneth Knowles  wrote:

> Does anyone have context on the status here? I know it is a new build.
> Perhaps it can be comment-triggered only until it is reliable enough that
> we would be willing to block merges on it?
>
> Kenn
>