Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Oddities in runner log parsing/detecting events #1037

Closed
Tracked by #1016
DavidGOrtega opened this issue May 30, 2022 · 0 comments · Fixed by #1030
Closed
Tracked by #1016

Oddities in runner log parsing/detecting events #1037

DavidGOrtega opened this issue May 30, 2022 · 0 comments · Fixed by #1030
Assignees
Labels
bug Something isn't working ci-github cml-runner Subcommand p0-critical Max priority (ASAP) technical-debt Refactoring, linting & tidying

Comments

@DavidGOrtega
Copy link
Contributor

DavidGOrtega commented May 30, 2022

Error parsing is making the runner to fail in GH having scenarios like:

  • runners never ending
  • runners being terminated at idletime even with ongoing jobs

To avoid them we had to include defensive code that was checking gh jobs. Expensive and also flaky

@DavidGOrtega DavidGOrtega changed the title Oddities in runner log parsing/detecting events @DavidGOrtega Oddities in runner log parsing/detecting events May 30, 2022
@DavidGOrtega DavidGOrtega added bug Something isn't working technical-debt Refactoring, linting & tidying p0-critical Max priority (ASAP) cml-runner Subcommand ci-github labels May 30, 2022
@DavidGOrtega DavidGOrtega self-assigned this May 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci-github cml-runner Subcommand p0-critical Max priority (ASAP) technical-debt Refactoring, linting & tidying
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant