In some scenarios, we get strange error while scaling up. It could be github api issue. But the main problem is if there is any issue before "Attempting to launch a new runner", We do not publish the retry payload. In this case, what's use of enabling retry?
{
"level": "INFO",
"message": "Received workflow_job.."
}
{
"level": "INFO",
"message": "Received event",
}
{
"level": "WARN",
"message": "Ignoring error: HttpError: <!DOCTYPE html>\r\n<!--\r\n\r\nHello future GitHubber! I bet you're here to remove those nasty inline styles,\r\nDRY up these templates and make 'em nice and re-usable, right?\r\n\r\nPlease, don't. https://github.com/styleguide/templates/2.0\r\n\r\n-->\r\n<html>\r\n <head>\r\n <title>Unicorn! · GitHub</title>\r\n <style type=\"text/css\" media=\"screen\">\r\n body {\r\n background-color: #f1f1f1;\r\n... "
}
In some scenarios, we get strange error while scaling up. It could be github api issue. But the main problem is if there is any issue before "Attempting to launch a new runner", We do not publish the retry payload. In this case, what's use of enabling retry?
Error log