[ 
https://issues.apache.org/jira/browse/BEAM-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662881#comment-16662881
 ] 

Valentyn Tymofieiev commented on BEAM-5812:
-------------------------------------------

Thanks for reporting; there was a similar flake earlier, and timeouts 
referenced by the test were somewhat random, see: 
https://issues.apache.org/jira/browse/BEAM-5415?focusedCommentId=16618246&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16618246.
 

Last time I looked at the failures, test framework did not provide enough 
output to correlate the Job ID with the test failure, which we should fix. At 
least we could make job names include the test name. 

See also: https://issues.apache.org/jira/browse/BEAM-5492.

I'm a little swamped right now but can try to take a look into the failures 
later in the week. If anyone has time to investigate this now, feel free to 
take it over.

> Timeout in Python ITs: WordCountIT (fn api and legacy), HourlyTeamScoreIT, 
> FastavroIT
> -------------------------------------------------------------------------------------
>
>                 Key: BEAM-5812
>                 URL: https://issues.apache.org/jira/browse/BEAM-5812
>             Project: Beam
>          Issue Type: Bug
>          Components: test-failures
>            Reporter: Kenneth Knowles
>            Assignee: Valentyn Tymofieiev
>            Priority: Critical
>              Labels: flake
>
> [https://builds.apache.org/job/beam_PostCommit_Python_Verify/6341/]
> [https://scans.gradle.com/s/ivjuxhni54azk/console-log?task=:beam-sdks-python:postCommitITTests]
> I don't see anything about these tests that would say much. It could be 
> environmental but it might just imply that all the timeouts should be higher 
> if they are sensitive, or their was (and continues to be) an outage of some 
> sort.
> Assignee chosen because I see you as reviewer of avro changes and author of 
> other changes to the py sdk in the last few days. If you have no idea, that's 
> fine, I just didn't want to leave it unassigned.
>  



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

Reply via email to