This is happening far too often with such a vital product of the GitHub stack. Our whole business[1] relies on GitHub Actions functioning. It just sucks. [1] https://buildjet.com/for-github-actions
Just a note that in your comparisons on your home page, you have a space after the 4 in "4 vCpu", but not after the 2 in "2vCpu". Github Action 2vCpu / 8 GB RAM BuildJet Runner 4 vCpu / 16 GB RAM Also, should probably be capitalized as "vCPU".
GitHub Having Issues
31–40 of 43 posts
Re: GitHub Having Issues
#32This is happening far too often with such a vital product of the GitHub stack. Our whole business[1] relies on GitHub Actions functioning. It just sucks. [1] https://buildjet.com/for-github-actions
Do you guys have customers?
Re: GitHub Having Issues
#33I literally set up some GitHub actions today for the first time in my life, I was really pumped about getting into the CI/CD game with my latest open repository. A couple of hours ago everything was going great, running a workflow needed maybe 40 seconds max. Now, they are not running at all. That all happened while I was thinkering with the yaml workflow file, so the disruption of the service made me believe that it…
If your test suite takes 40 seconds, is it not quicker and easier to run locally than the overhead of another git commit to get feedback?
Re: GitHub Having Issues
#34I literally set up some GitHub actions today for the first time in my life, I was really pumped about getting into the CI/CD game with my latest open repository. A couple of hours ago everything was going great, running a workflow needed maybe 40 seconds max. Now, they are not running at all. That all happened while I was thinkering with the yaml workflow file, so the disruption of the service made me believe that it…
> running a workflow needed maybe 40 seconds max If your test suite takes 40 seconds, is it not quicker and easier to run locally than the overhead of another git commit to get feedback?
On CI it takes about 5 minutes to run.
My laptop which while not top of the line is fairly well powered (8core 32 gb) the fan starts spinning and slows down a bit whenever I run the suite.
I find both these times incredibly distracting and inefficient. It breaks my concentration, faster feedback would be really nice.
Re: GitHub Having Issues
#35Earlier quoted context omitted.
> running a workflow needed maybe 40 seconds max If your test suite takes 40 seconds, is it not quicker and easier to run locally than the overhead of another git commit to get feedback?
On a recent project I am working on tests typically take 60 seconds to run. This is jest with testing-library, with 2000 tests fairly typical setup. On CI it takes about 5 minutes to run. My laptop which while not top of the line is fairly well powered (8core 32 gb) the fan starts spinning and slows down a bit whenever I run the suite. I find both these times incredibly distracting and inefficient. It breaks my conce…
Re: GitHub Having Issues
#36I literally set up some GitHub actions today for the first time in my life, I was really pumped about getting into the CI/CD game with my latest open repository. A couple of hours ago everything was going great, running a workflow needed maybe 40 seconds max. Now, they are not running at all. That all happened while I was thinkering with the yaml workflow file, so the disruption of the service made me believe that it…
> running a workflow needed maybe 40 seconds max If your test suite takes 40 seconds, is it not quicker and easier to run locally than the overhead of another git commit to get feedback?
If I'm making a change and I want feedback from the test suite, of course I'd run it locally.
Re: GitHub Having Issues
#37Earlier quoted context omitted.
Do you guys have customers?
Yes, we do! We launched 20 days ago and should soon be ramen profitable.
Re: GitHub Having Issues
#38Let's hope they didn't push faulty DNS records :D But seriously, what's going on with all the service disruptions? From slack to all of facebook to GitHub (who had 7 incidents in September). Maybe centralizing the whole internet into a few providers isn't a good idea after all?
> Maybe centralizing the whole internet into a few providers isn't a good idea after all? Everything's tradeoffs, economies of scale for centralising- easy to blame the provider if a fuckup happens. But when it goes down it stops everything; same issue with AWS, Azure's ADFS, Cloudflare, ad infinitum. Half the internet can go away at a moments notice or the provider can turn on you personally because an automated bot…
Is there any particular source for that or is it just something that you've noticed? Feel like I do see more around this time of year but would be real interested if there is data backing it up.
Re: GitHub Having Issues
#39Re: GitHub Having Issues
#40Is https://gist.github.com down for everyone or it's just me? Not able to access it since weeks now.