mirror of
https://github.com/neondatabase/neon.git
synced 2026-01-14 08:52:56 +00:00
68cf0ba439
## Problem Ref: https://github.com/neondatabase/cloud/issues/23314 We suspect some inconsistency in Benchmark tests runs could be due to different type of runners they are landed in. To have that aligned in both terms: failure rates and benchmark results, lets run them for now on `small-metal` servers and see the progress for the tests stability. ## Summary of changes
30 lines
756 B
YAML
30 lines
756 B
YAML
self-hosted-runner:
|
|
labels:
|
|
- arm64
|
|
- large
|
|
- large-arm64
|
|
- small
|
|
- small-metal
|
|
- small-arm64
|
|
- us-east-2
|
|
config-variables:
|
|
- AZURE_DEV_CLIENT_ID
|
|
- AZURE_DEV_REGISTRY_NAME
|
|
- AZURE_DEV_SUBSCRIPTION_ID
|
|
- AZURE_PROD_CLIENT_ID
|
|
- AZURE_PROD_REGISTRY_NAME
|
|
- AZURE_PROD_SUBSCRIPTION_ID
|
|
- AZURE_TENANT_ID
|
|
- BENCHMARK_PROJECT_ID_PUB
|
|
- BENCHMARK_PROJECT_ID_SUB
|
|
- REMOTE_STORAGE_AZURE_CONTAINER
|
|
- REMOTE_STORAGE_AZURE_REGION
|
|
- SLACK_UPCOMING_RELEASE_CHANNEL_ID
|
|
- DEV_AWS_OIDC_ROLE_ARN
|
|
- BENCHMARK_INGEST_TARGET_PROJECTID
|
|
- PGREGRESS_PG16_PROJECT_ID
|
|
- PGREGRESS_PG17_PROJECT_ID
|
|
- SLACK_ON_CALL_QA_STAGING_STREAM
|
|
- DEV_AWS_OIDC_ROLE_MANAGE_BENCHMARK_EC2_VMS_ARN
|
|
- SLACK_ON_CALL_STORAGE_STAGING_STREAM
|