[
https://issues.apache.org/jira/browse/BEAM-10985?focusedWorklogId=494056&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-494056
]
ASF GitHub Bot logged work on BEAM-10985:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Oct/20 16:36
Start Date: 02/Oct/20 16:36
Worklog Time Spent: 10m
Work Description: kennknowles commented on pull request #13000:
URL: https://github.com/apache/beam/pull/13000#issuecomment-702834952
Isn't this "potential downside" a major problem? How do up to date checks
work then?
----------------------------------------------------------------
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: 494056)
Time Spent: 1h 50m (was: 1h 40m)
> Python precommit flakes when publishing test report
> ---------------------------------------------------
>
> Key: BEAM-10985
> URL: https://issues.apache.org/jira/browse/BEAM-10985
> Project: Beam
> Issue Type: Bug
> Components: test-failures
> Reporter: Kyle Weaver
> Assignee: Kyle Weaver
> Priority: P2
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> https://ci-beam.apache.org/job/beam_PreCommit_Python_Commit/15450/console
> The Jenkins job fails when trying to publish results:
> 13:50:49 ERROR: Step ‘Publish JUnit test result report’ failed: No test
> report files were found. Configuration error?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
