[
https://issues.apache.org/jira/browse/BEAM-8481?focusedWorklogId=334445&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-334445
]
ASF GitHub Bot logged work on BEAM-8481:
----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Oct/19 00:01
Start Date: 26/Oct/19 00:01
Worklog Time Spent: 10m
Work Description: tvalentyn commented on pull request #9896: [BEAM-8481]
Increasing Py3.7 postcommit job timeout after 120 minutes instead of 100
URL: https://github.com/apache/beam/pull/9896#discussion_r339274361
##########
File path: .test-infra/jenkins/job_PostCommit_Python37.groovy
##########
@@ -27,7 +27,7 @@
PostcommitJobBuilder.postCommitJob('beam_PostCommit_Python37', 'Run Python 3.7 P
previousNames('/beam_PostCommit_Python3_Verify/')
// Set common parameters.
- commonJobProperties.setTopLevelMainJobProperties(delegate)
+ commonJobProperties.setTopLevelMainJobProperties(delegate, 'master', 120)
Review comment:
Does groovy allow to pass key-value pairs here, so that we ca avoid passing
'master'?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 334445)
Time Spent: 20m (was: 10m)
> Python 3.7 Postcommit test -- frequent timeouts
> -----------------------------------------------
>
> Key: BEAM-8481
> URL: https://issues.apache.org/jira/browse/BEAM-8481
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Ahmet Altay
> Assignee: Valentyn Tymofieiev
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> [https://builds.apache.org/job/beam_PostCommit_Python37/] – this suite
> seemingly frequently timing out. Other suites are not affected by these
> timeouts. From the history, the issues started before Oct 10 and we cannot
> pinpoint because history is lost.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
