Skip to content

PYTHON-5388 - AI/ML Testing Pipeline Automatic Retries #106

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
NoahStapp merged 8 commits into from
Dec 2, 2025
Merged

PYTHON-5388 - AI/ML Testing Pipeline Automatic Retries #106

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
8cefd06
PYTHON-5388 - Add two automatic retries
NoahStapp Dec 2, 2025
c858b0d
Fix EXIT_CODE
NoahStapp Dec 2, 2025
efc457a
Fix EXIT_CODE
NoahStapp Dec 2, 2025
867f5f2
debugging
NoahStapp Dec 2, 2025
ded8625
Cleanup
NoahStapp Dec 2, 2025
2865c88
Linting
NoahStapp Dec 2, 2025
91ca8ff
Update README
NoahStapp Dec 2, 2025
0282908
Update wording
NoahStapp Dec 2, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 22 additions & 1 deletion .evergreen/execute-tests.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,4 +13,25 @@ set +a

cd ${REPO_NAME}

bash ${ROOT_DIR}/${DIR}/run.sh
MAX_ATTEMPTS=3
ATTEMPT=1
EXIT_CODE=0
set +e

while [ $ATTEMPT -le $MAX_ATTEMPTS ]; do
bash ${ROOT_DIR}/${DIR}/run.sh

EXIT_CODE=$?

if [ $EXIT_CODE -eq 0 ]; then
break
else
echo "Tests failed on attempt $ATTEMPT of $MAX_ATTEMPTS..."
((ATTEMPT++))
fi
done

if [ $EXIT_CODE -ne 0 ]; then
echo "Tests failed after $MAX_ATTEMPTS attempts."
fi
exit $EXIT_CODE
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -187,7 +187,7 @@ evergreen patch -p ai-ml-pipeline-testing --param REPO_ORG=caseyclements --param

### Handling Failing Tests

Tests are run periodically (nightly) and any failures will propagate into both the `dbx-ai-ml-testing-pipline-notifications` and `dbx-ai-ml-testing-pipeline-notifications-{language}` channel. Repo owners of this `ai-ml-testing-pipeline` library are required to join the `dbx-ai-ml-testing-pipeline-notifications`. Pipeline specific implementers must **at least** join `dbx-ai-ml-testing-pipline-notifications-{language}` (e.g. whomever implemented `langchain-js` must at least be a member of `dbx-ai-ml-testing-pipeline-notifications-js`).
Tests are run periodically (nightly). All failing test suites are automatically retried up to two times. Any failures will propagate into both the `dbx-ai-ml-testing-pipline-notifications` and `dbx-ai-ml-testing-pipeline-notifications-{language}` channel. Repo owners of this `ai-ml-testing-pipeline` library are required to join the `dbx-ai-ml-testing-pipeline-notifications`. Pipeline specific implementers must **at least** join `dbx-ai-ml-testing-pipline-notifications-{language}` (e.g. whomever implemented `langchain-js` must at least be a member of `dbx-ai-ml-testing-pipeline-notifications-js`).

If tests are found to be failing, and cannot be addressed quickly, the responsible team MUST create a JIRA ticket within their team's project (e.g. a python failure should generate an `INTPYTHON` ticket), and disable the relevant tests
in the `config.yml` file, with a comment about the JIRA ticket that will address it.
Expand Down