Builds hanging in pre-build setup step for 2+ days across multiple repos

Deployment
1

Hi Travis CI Support,

All our builds have been failing for the past 2 days across multiple repositories. After analyzing the raw job logs, we have identified the exact failure point — builds are hanging during Travis’s internal infrastructure setup steps, before any of our .travis.yml configuration is executed.

Failure Pattern:

On dist: focal builds, the hang occurs at the fix_perforce_key setup event. In the passing build, this step completes and prints OK. In the stuck build, the event starts but never completes, producing zero output until Travis’s 10-minute no-output timer fires and kills the job.

On dist: jammy builds, the hang occurs immediately after update_apt_keys completes, before fix_hhvm_source begins.

In both cases, the build is terminated with:

“No output has been received in the last 10m0s”

Comparison of Job Logs from our 2 repos:

Passing Stuck
repo_A (focal) Job 639395966 Job 639441032
repo_B (jammy) Job 639432471 Job 639440373

All four jobs share:

  • Worker version: deploy_2025.08.20.CI.1

  • focal VM image: travis-ci-ubuntu-2004-1761808138-4ffea187-dirty

  • jammy VM image: travis-ci-ubuntu-2204-1761745415-2d890300-dirty

  • travis-build version: 2812e526

The VM images, worker versions, and build configurations are identical between passing and failing jobs. No changes were made to our CI configuration.

What we have ruled out:

  • Not a cache issue (tested with cache: false)

  • Not a dist pinning issue (both focal and jammy are affected)

  • Not application code or dependency related (hang occurs before git clone in some cases)

  • Not a Travis platform-wide outage (status page shows green)

  • Not a GCP zone issue (both passing and failing builds ran on gce-production-1)

Could you plz help figure out why the fix_perforce_key and post-update_apt_keys setup steps are intermittently hanging on your worker infrastructure.

2

We have the same issue. For the fix_perforce_key it seems that the package.perforce.com where the key is downloaded from is not available and so the wget command just hangs and never resolves.
This is according to:

Didn’t check the other one, but it may be a similar issue. Would be nice to get an update on that from the travis team (if they read this forum)

3

I report the same exact issue on all our Travis builds for our company.

Hanging out and timing out after 10 minutes.

Our builds use focal as a Ubuntu dist, did a test with noble but the problem persists

4

Up we have the same problem here

5

Same problem here

6

Same problem here as well, since May 24th.

7

Same exact issue here, affecting all configured repos, some using Node runtime and others using Python. Seems unrelated to the runtime/language of the repo. Using focal dist as well

8

Also having the same issue, all builds failing across multiple languages.

9

Same problem here :frowning:

10

Also having the same issue…