mirror of
https://github.com/temporalio/temporal.git
synced 2026-08-30 18:41:49 -07:00
65a58d987c
## What changed? Add workflow dispatch options to the functional tests Github Action to allow us to run n-iterations of a single functional test with a configurable timeout. There is also an option to run n-iterations of a single unit test, although it may be faster to run that locally. WARNING: For functional tests, this will definitely be oomkilled for n>=100, likely for n=>50 too. I suggest to start with n=20 to see how the memory goes and then increase from there. Different DBs may use different amounts of RAM also. ## Why? To aid in the diagnosis and treatment of flaky tests. ## How did you test it? Tested in github actions. Here is the action run normally, with no new input parameters: https://github.com/temporalio/temporal/actions/runs/11261156403 Here is the action run on one test multiple times: https://github.com/temporalio/temporal/actions/runs/11261236304 While we still have buildkite, the uploaded test results will be uploaded. You can find them by going to https://buildkite.com/organizations/temporal/analytics/suites/temporal-public/runs?branch=all+branches and looking for a recent run with `"job: functional-test"` and the commit hash you used. Here is the buildkite output of the run above: https://buildkite.com/organizations/temporal/analytics/suites/temporal-public/runs/39901afd-35f1-8171-9257-e0bada374824 ## Potential risks Our functional test pipeline could be broken by this PR, but we would notice that pretty immediately ## Documentation How to run it yourself 1. Go to https://github.com/temporalio/temporal/actions/workflows/run-tests.yml 2. Click "run workflow" on the upper right hand side 5. Set Commit SHA to the latest commit on the branch 6. Select your desired options 7. Click the green "Run workflow" button ## Is hotfix candidate? <!-- Is this PR a hotfix candidate or does it require a notification to be sent to the broader community? (Yes/No) -->
27 lines
886 B
Bash
27 lines
886 B
Bash
#!/bin/sh
|
|
|
|
if [ -z "$BUILDKITE_ANALYTICS_TOKEN" ]; then
|
|
echo "BUILDKITE_ANALYTICS_TOKEN is not set. Skipping."
|
|
exit 0 # we don't want the script to fail here
|
|
fi
|
|
|
|
echo "uploading test results from $(pwd)"
|
|
|
|
for file in *.junit.xml; do
|
|
[ -e "$file" ] || continue
|
|
echo "uploading ${file}"
|
|
|
|
curl -i -X POST \
|
|
-H "Authorization: Token token=${BUILDKITE_ANALYTICS_TOKEN}" \
|
|
-F "data=@${file}" \
|
|
-F "format=junit" \
|
|
-F "run_env[CI]=github_actions" \
|
|
-F "run_env[key]=${GITHUB_ACTION}-${GITHUB_RUN_NUMBER}-${GITHUB_RUN_ATTEMPT}" \
|
|
-F "run_env[number]=${GITHUB_RUN_NUMBER}" \
|
|
-F "run_env[branch]=${GITHUB_REF}" \
|
|
-F "run_env[commit_sha]=${GITHUB_SHA}" \
|
|
-F "run_env[url]=https://github.com/${GITHUB_REPOSITORY}/actions/runs/${GITHUB_RUN_ID}" \
|
|
-F "run_env[message]=${BUILDKITE_MESSAGE}" \
|
|
https://analytics-api.buildkite.com/v1/uploads
|
|
done
|