[
https://issues.apache.org/jira/browse/BEAM-13958?focusedWorklogId=728361&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-728361
]
ASF GitHub Bot logged work on BEAM-13958:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Feb/22 17:00
Start Date: 16/Feb/22 17:00
Worklog Time Spent: 10m
Work Description: TheNeuralBit commented on pull request #16871:
URL: https://github.com/apache/beam/pull/16871#issuecomment-1041880453
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 728361)
Time Spent: 20m (was: 10m)
> XVR Spark failing on 2.37.0 release branch
> ------------------------------------------
>
> Key: BEAM-13958
> URL: https://issues.apache.org/jira/browse/BEAM-13958
> Project: Beam
> Issue Type: Bug
> Components: cross-language, runner-spark
> Reporter: Brian Hulette
> Assignee: Brian Hulette
> Priority: P2
> Time Spent: 20m
> Remaining Estimate: 0h
>
> :runners:spark:2:job-server:validatesCrossLanguageRunnerGoUsingJava and
> :runners:spark:3:job-server:validatesCrossLanguageRunnerGoUsingJava are
> failing on the 2.37.0 release branch:
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark_PR/123
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3_PR/59
> This task was failing on master at the time the branch was cut:
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1277/
> It was resolved shortly after:
> https://ci-beam.apache.org/job/beam_PostCommit_XVR_Spark3/1280/
> (Note the signal in these suites is a little obscured due to other flakes,
> but there seems to have been a hard failure in
> :job-server:validatesCrossLanguageRunnerGoUsingJava for :runners:spark:2 and
> :runners:spark:3.)
> Unfortunately I'm not clear which change listed in 1280 resolved the issue.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
