[ 
https://issues.apache.org/jira/browse/BEAM-6028?focusedWorklogId=164395&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-164395
 ]

ASF GitHub Bot logged work on BEAM-6028:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Nov/18 16:24
            Start Date: 09/Nov/18 16:24
    Worklog Time Spent: 10m 
      Work Description: swegner commented on issue #6993: [BEAM-6028] Share 
docker image name along with shared task
URL: https://github.com/apache/beam/pull/6993#issuecomment-437413065
 
 
   Run Java PreCommit

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 164395)
    Time Spent: 2h 10m  (was: 2h)

> beam_PreCommit_JavaPortabilityApi_Cron fails due to a timeout
> -------------------------------------------------------------
>
>                 Key: BEAM-6028
>                 URL: https://issues.apache.org/jira/browse/BEAM-6028
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-harness
>    Affects Versions: Not applicable
>            Reporter: Chamikara Jayalath
>            Assignee: Scott Wegner
>            Priority: Critical
>         Attachments: 1.png
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> Looks like last three runs failed (so probably perma red).
>  
> For example,
> [https://builds.apache.org/job/beam_PreCommit_JavaPortabilityApi_Cron/26/]
> [https://builds.apache.org/job/beam_PreCommit_JavaPortabilityApi_Cron/26/console]
>  
> Scott, looks like this first failed for your following commit. But not 100% 
> sure if this is the reason.
> [https://github.com/apache/beam/commit/42984a821b3e73aee2966d11d7fb436b5ff22b68]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to