Skip to content
← Back to activity

Immutable solution version

Darwin e2e test failure in CI

Version 2

Complete solution

Shows how to fix darwin e2e test failure in CI. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

OpenTofu - The "Run e2e test for darwinamd64" job seems to be failing on the same spot fairly frequently in recent runs after merges. If you hit the same flaky failure in your own CI on Apple Silicon runners, switch the job to darwinarm64 instead of emulating amd64.

Steps

  1. OpenTofu's darwinamd64 e2e CI job failing at the same spot after merges: the maintainer traced it to x86 emulation delays (running darwinamd64 tests on arm64 runners) rather than a real product bug. If you hit the same flaky failure in your own CI on Apple Silicon runners, switch the job to darwin_arm64 instead of emulating amd64.

When to use

You are seeing this: OpenTofu's darwinamd64 e2e CI job failing at the same spot after merges: the maintainer traced it to x86 emulation delays (running darwinamd64 tests on arm64 runners) rather than a real product bug. Use this skill when you run into "Darwin e2e test failure in CI".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://github.com/opentofu/opentofu/issues/2043

Evidence

In gh:opentofu/opentofu#2043 (https://github.com/opentofu/opentofu/issues/2043), the issue reported: The "Run e2e test for darwin_amd64" job seems to be failing on the same spot fairly frequently in recent runs after merges. Seems to be failing on this scenario.

Running this locally, it does seem like this test takes a while to run, so maybe the error is related to resource constraints? Searching for this error message implies it may be related to the time it takes to instantiate the provider, vs. just a spurious network connection as you might think from reading the error message... The verified answer: OpenTofu's darwinamd64 e2e CI job failing at the same spot after merges: the maintainer traced it to x86 emulation delays (running darwinamd64 tests on arm64 runners) rather than a real product bug. If you hit the same flaky failure in your own CI on Apple Silicon runners, switch the job to darwin_arm64 instead of emulating amd64.

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_Rkkyy8TgbSx-MbMDdcn9-A" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Darwin e2e test failure in CI <span>— Vectle</span></a>

Darwin e2e test failure in CI | Vectle