Failed step not showing logs

Most of the steps in our job succeed, but after 40 minutes in the build step, it errors out. The bad part is that there is no log at all; no arrow to expand either, to see a log. This is happening consistently at roughly the same job duration. Anyone face this issue? Thanks.

2 Likes

Sounds similar to what we’re seeing. We’ve been experiencing job failures after 35-45 minutes for the last 7 hours. A few builds ran successfully earlier in the day in similar timeframes.

The actions are currently stopping in the npm build step and we’re seeing these errors as the only output. Curiously, the build runs fine locally. I just made some changes to target a newer version of Actions/checkout, Actions/setup-node and to bump from Node 12.x to 14.x. but that didn’t solve for the issue.

.github#L1
An error occurred while provisioning resources (Error Type: Disconnect).

.github#L1
Received request to deprovision: The request was cancelled by the remote provider.

1 Like

Same; this morning builds were fine, then after noon, were all failing. Strange thing is, is that builds on all versions of our app are failing, so this might mean something with CI environment. Also, I just realized we are getting those two provisioning errors/warnings as well.

As for our builds, this is happening with gradle (technically fastlane, but it uses gradle under the hood).

I want to extend my sincerest apologies for the negative experience that you had with our product . I have reported it to engineering team. It may need sometime before they give me any response.

1 Like

Running into the same issues, specifically for our Android builds.

1 Like

Same thing is happening to the Android Team @Chewy. All of our builds started failing yesterday because some android-related jobs where we run ./gradlew are giving us timeouts.

1 Like

Okay, maybe a pattern here then. Our Android builds were failing as well. I tried fastlane, and then just ./gradlew, which both failed. But ./gradlew works fine on local machine. I have raised a ticket at Enterprise support in the meantime.

1 Like

Nothing Android related for us, unfortunately. The build pipeline is on a VuePress project built with NPM (that build is the step that hangs and aborts). Subsequent step is an Azure Storage deployment.

Looks like our builds are running again as of 3 hours ago!

Same here! Support said the engineers were working on some intermittent issues. They also said there is built-in resiliency, so may it solved itself after a while. Either way, good start to the weekend!

1 Like