[
https://issues.apache.org/jira/browse/BEAM-10913?focusedWorklogId=664271&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-664271
]
ASF GitHub Bot logged work on BEAM-10913:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Oct/21 19:35
Start Date: 12/Oct/21 19:35
Worklog Time Spent: 10m
Work Description: aaltay commented on pull request #15663:
URL: https://github.com/apache/beam/pull/15663#issuecomment-941360496
@fernando-wizeline - I think there are 2 options. We could look into the
metrics cluster logs
(https://cloud.google.com/kubernetes/clusters/details/us-central1-a/metrics/nodes?project=apache-beam-testing)
and tried to root cause the problem. I have tried this but I was not
successful. Or we could revert this and other configuration changes and push
the metrics again.
Btw, is the metrics staging environment running as expected? Or is it also
failing?
--
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: 664271)
Time Spent: 13h 50m (was: 13h 40m)
> Post-commit github actions status
> ---------------------------------
>
> Key: BEAM-10913
> URL: https://issues.apache.org/jira/browse/BEAM-10913
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Alan Myrvold
> Assignee: Fernando Morales
> Priority: P3
> Time Spent: 13h 50m
> Remaining Estimate: 0h
>
> Add status for post-commit github actions to find flaky and consistently
> failing tests
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
