Hosted macOS workflows will experience longer wait times the week of December 14th. #2247
Comments
|
Good luck on your work. I wonder, if there will be any discounts on macOS hosted github-actions in this time interval? |
|
Does this maintenance include fixing the network issues with macOS? |
The problem is that there is no way to re-run individual jobs in GitHub Actions so far. EDIT: This means that discounts only on macOS-hosted GitHub Actions would not remediate the problem because the only way to re-run those jobs is to re-run the entire workflow, incurring additional cost for jobs that run on non-macOS platforms (because they will have to be re-run, even if they had already run, and succeeded). |
|
Volleyball geil |
|
Thank you |
|
Nice |
|
Quite bad timing knowing that App Store Connect is going on holiday next week and everyone rushes to release their apps. |
|
I'm also facing network issues when installing yarn packages on a MacOS runner. I get error messages similar to the ones shown by @styfle , has this issue been identified and will the maintenance try to fix it, or should I raise it to the Github support? |
@styfle actually it's a bug from yarn. yarnpkg/yarn#8242 The reason for this bug is that the macOS host disk is slow, and extra large number of files from npm package such as Maybe you have already observed that this issue always happened on |
|
@Brooooooklyn Its not just yarn that fails, all network requests fail eventually. Even spawning a server on localhost will sometimes fail with ECONNREFUSED. |
|
@styfle can you provide repro steps? I want to try and chase that down. |
|
@nodeselector Thanks! The yarn issue should be easy to reproduce because it fails early. Create a repo with this package.json and yarn.lock in the root. And then create a workflow that runs on:
push:
branches:
- master
tags:
- '!*'
pull_request:
jobs:
test:
timeout-minutes: 15
strategy:
fail-fast: false
matrix:
os: [macos-latest]
node: [10, 12]
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@v2
with:
fetch-depth: 100
- uses: actions/setup-node@v1
with:
node-version: ${{ matrix.node }}
- run: yarn install |
|
Y'all are amazing |
|
Awesome indeed. |
|
WebDav binary codes are not authentic. The codes were submitted by William (Dav)id Smith. DOB 7-23-1977. He stole the codes off my Moto e5 Plus. Pur a virus on my device deleted my Gmail account, deleted my outlook account, and deleted my yahoo. Then submitted the data on github and VLC media as a decoder (DAV 1D IS AV 1 DECODER :D). This is why the network is all messed up. Ive been back tracing his steps and fixing everything. Most of the time all I do is search the web and the sites that appear in the suggestions is mostly ones that ge is on. He has been using my gmail & everytime i ask him to stop using it he denies it. It is to the point where I've had enough. Ive tried to make police reports and they do jot take cyber crime serious around here. So I am going to hire a lawyer ti getbthe process on tge ball. They i can claim my assets. |
|
Why is it a issue this week we need these systems running what can we do |
|
we need to boost the server speed it needs a severe enhanced signal |
Try to not merge them so many times only merge them about 4 times a day and even when you merge them you need to filter out all the bad ones |
|
Keep it simple try to earn only merge maybe 3 times a day don't repeat process is more than you need to keep it simple go back to the basics |
|
You're overworking the computer is confusing it and when you get confused you can't function so you need to make sure the computers okay |
|
Think about it a computers like a little kid is going to do exactly what you tell it to do but if you overwork it it's going to shut down a computer is like a body if you don't get that what it needs then it can't survive and it can't function |
You need to take that yarn completely out |
|

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.










Breaking changes
GitHub's macOS datacenter is performing scheduled maintenance December 14-18. During this time customers may experience longer than normal wait times for their macOS workflows to begin.
Target date
December 14-18
Possible impact
Jobs using any of the macOS virtual environments may experience longer than normal queue times. In some cases it's possible workflows will time out, be cancelled, and need to be restarted.
Virtual environments affected
The text was updated successfully, but these errors were encountered: