You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since a few days, the duration of the actions/checkout@v3 steps on windows-2019 have dramatically increased.
This behavior is seen on all my repos (all private). Below a table showing an example of before/after.
Checkout step
Feb 17th
Feb 21st
1
13s
1m35s
2
8s
47s
The result is a huge increase in build (and billable) time.
The github status page does show some issues around this time frame, but these were all solved:
Platforms affected
Azure DevOps
GitHub Actions - Standard Runners
GitHub Actions - Larger Runners
Runner images affected
Ubuntu 18.04
Ubuntu 20.04
Ubuntu 22.04
macOS 11
macOS 12
Windows Server 2019
Windows Server 2022
Image version and build link
Current runner version: '2.301.1'
Operating System
Microsoft Windows Server 2019
10.0.17763
Private repo
Is it regression?
Yes, sorry private repos
Expected behavior
The build times should be fairly constant.
Actual behavior
Build times explode. Burning down our build minutes too fast.
Repro steps
Compare build times on any windows environment from before Feb 18th with today.
The text was updated successfully, but these errors were encountered:
Hello! Please report to the https://github.com/actions/checkout repo as they maintain the setup task primarily and can tell what happens on windows better.
Description
Since a few days, the duration of the
actions/checkout@v3
steps onwindows-2019
have dramatically increased.This behavior is seen on all my repos (all private). Below a table showing an example of before/after.
13s
1m35s
8s
47s
The result is a huge increase in build (and billable) time.
The github status page does show some issues around this time frame, but these were all solved:
Platforms affected
Runner images affected
Image version and build link
Private repo
Is it regression?
Yes, sorry private repos
Expected behavior
The build times should be fairly constant.
Actual behavior
Build times explode. Burning down our build minutes too fast.
Repro steps
Compare build times on any windows environment from before Feb 18th with today.
The text was updated successfully, but these errors were encountered: