🛠️ Tuist Run Report 🛠️
Tests 🧪
| Scheme | Status | Cache hit rate | Tests | Skipped | Ran | Commit |
|---|---|---|---|---|---|---|
| TuistAcceptanceTests | ✅ | 0 % | 0 | 0 | 0 | ef6c54378 |
Builds 🔨
| Scheme | Status | Duration | Commit |
|---|---|---|---|
| TuistAcceptanceTests | ✅ | 4m 3s | ef6c54378 |
Hive
GitHub issue · Closed
tuist account and create random projects under it, instead of creating random temporary organizations.TUIST_FEATURE_FLAG_KURA from the acceptance test step, so the canary leg exercises Kura again.kura worker pool labeled with node.cluster.x-k8s.io/pool=kura, matching the scheduler selector used by Kura pods.Kura servers are scoped to an account. In canary, the Kura servers are bound to tuist, but the acceptance tests were creating temporary organizations. With TUIST_FEATURE_FLAG_KURA=1, those temporary accounts requested Kura endpoints and got no usable endpoint back, which led the CLI into a bad cache URL path.
There was also an infrastructure issue in canary: the Kura StatefulSet pods were pending because they select node.cluster.x-k8s.io/pool=kura, but the cluster had no nodes with that pool label.
The acceptance tests create isolated random projects while using the account that owns the canary Kura nodes. When Kura is unavailable or has no endpoints, clients still receive the normal cache endpoints instead of an empty list.
swiftformat cli/Sources/TuistAcceptanceTesting/TuistAcceptanceTestFixtureTestingTrait.swift cli/Tests/TuistCacheEEAcceptanceTests/TuistCacheEECanaryAcceptanceTests.swifttuist installmise run cli:eeTUIST_EE=1 tuist generate TuistAcceptanceTesting TuistCacheEEAcceptanceTests --no-openxcodebuild build -workspace Tuist.xcworkspace -scheme TuistCacheEEAcceptanceTests CODE_SIGNING_ALLOWED=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY=""mix format --check-formatted lib/tuist/accounts.ex test/tuist_web/controllers/api/cache_controller_test.exsMIX_ENV=test mix ecto.resetmix test test/tuist_web/controllers/api/cache_controller_test.exsgit diff --check origin/main...HEADkubectl: kura-tuist-eu-central-1-0 was pending because no node matched node.cluster.x-k8s.io/pool=kura.| Scheme | Status | Cache hit rate | Tests | Skipped | Ran | Commit |
|---|---|---|---|---|---|---|
| TuistAcceptanceTests | ✅ | 0 % | 0 | 0 | 0 | ef6c54378 |
| Scheme | Status | Duration | Commit |
|---|---|---|---|
| TuistAcceptanceTests | ✅ | 4m 3s | ef6c54378 |