➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2021-12-30 11:06 by mark.dickinson, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Pull Requests | |||
|---|---|---|---|
| URL | Status | Linked | Edit |
| PR 30301 | merged | mark.dickinson, 2021-12-30 11:07 | |
| Messages (1) | |||
|---|---|---|---|
| msg409359 - (view) | Author: Mark Dickinson (mark.dickinson) *  |
Date: 2021-12-30 11:06 | |
Recently there was an upstream issue with GitHub Actions that caused the Windows build steps in build.yml to hang. No output for the step was displayed in the build logs until the entire job was eventually cancelled, after the default step timeout of 6 hours. I don't know how to fix the "no output" problem, but we can mitigate the 6 hour wait by adding a timeout for the build step. Some external discussion suggested that a conservative timeout of 30 minutes would be appropriate; looking at recent PRs, the build usually completes in around 5 minutes. The (soon-to-be-)attached PR adds that timeout. Here's the log from one of the failed jobs: https://github.com/python/cpython/runs/4641823914?check_suite_focus=true (note that this link will probably eventually become invalid). Here's the relevant GitHub incident: https://www.githubstatus.com/incidents/gh0vvxtlj5v7 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:54 | admin | set | github: 90361 |
| 2022-01-09 10:30:13 | mark.dickinson | set | status: open -> closed stage: patch review -> resolved |
| 2021-12-30 11:07:48 | mark.dickinson | set | keywords:
+ patch stage: patch review pull_requests: + pull_request28513 |
| 2021-12-30 11:06:59 | mark.dickinson | create | |