Build abort via Bitrise DEN (timeout)

#1

Bitrise Build Issue Report template

Description of the issue

Workflow runs are timing out with the message “Abort via Bitrise DEN (timeout)” for random builds. Nothing apparent has changed in the meantime.

Environment:

Bitrise.io -> macOS 10.14.6 (Mojave)

Which build Step causes the issue and which version of the step?

Workflow run times out

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : Sometimes
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : YES/NO
  • Does the issue happen sporadically, or every time? : sporadically
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : 16th March, 2020

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

Not reproducible in local debug

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( https://www.bitrise.io/cli )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/ .

Build log

0 Likes

#2

Hi @DharmendraVolansys

Could you please send me a previous build URL on the same workflow that didn’t time out?

0 Likes

#3

Hi @ahvth-bitrise

Please find below the URL for the previous build.

0 Likes

#4

Hi @ahvth-bitrise

Do we have any update on the issue?
Let me know if any further information is required.

0 Likes

#5

Hi There,

Is there any update regarding the issue?
We are still facing this issue.

0 Likes

#6

Hi @DharmendraVolansys,

Really sorry for the huge delay.

These cases are always hard to address since we don’t have access to your git history, but since the example you provided is so close to timing out too, we are not able to locate an issue on our side it just seems that this workflow is overly ambitious.

We’d recommend separating this into different workflow as currently it contains three different archive steps which are indeed really hard to fit into a single workflow.

0 Likes

#7

Thanks for the response, @bitce

This random timeout issue we started facing from 16th March 2020. We have the same workflow running with three different archives from the start. We haven’t face this issue before 16th March 2020.

0 Likes

#8

I see! Can you rebuild these workflows in succession afterwards? Can you perhaps paste a few more examples and enable Support User access in the Settings of the app?

0 Likes

#9

HI @bitce,

We have enabled the Support User access in the app. Please find below the recent examples for the timeout issue:

19th May 2020

18th May, 2020

15th May, 2020

14th May, 2020

0 Likes

#10

Hi @bitce,

Is there any update regarding the issue?
Let me know if any further information is required.

0 Likes