We’re encountering 2x degraded performance, meaning we’ve had to double our resource class, and still getting killed processes.
This is an urgent priority for us as it’s meaning our CI just won’t even run, let alone doubling our costs.
V2 run with double resource + killed:
bcafd6c0-65ca-4bf0-80a3-32f4a2a912cc
V2 run without doubling resource class:
2bd09640-83c3-4d62-8125-e27370b99d41
V1 - no issues:
fdb9393e-403d-485d-9bfc-07508c833996
Would appreciate a techie looking at this urgently as well as clarification on if you’ll issue billing corrections for the extra resources and failed runs? This is the kind of thing that erodes trust and costs enormous amounts of staff time while we can’t operate correctly.
I’ve opted your org out, it should take about 10 minutes to apply. Please let me know if you’re still seeing Jobs running on the V1 runtime after that.
Hi, we’re currently facing issues in that the first run always failed with signal: killed. After rerunning the ci, it passes. Can I get any advice to solve this issue?
Hello!
Our org seems to have been upgraded to v2 container the other day.
The CI that used to take 6 or 7 minutes took 3 hours and finally failed.
Please opt out our org.
It’s a tricky one. It doesn’t line up with the project being opt’ed in to v2. But looking at the timeline of your issues it could be related to a small bug that got introduced yesterday.
A fix for it has just been rolled out, would you be able to retry your failing job please?