[lym953]

Problem

When pip install fails for a Python test function, the "build python lambdas" job still passes. The deployed function then has only its handler file and no dependencies, and the failure shows up later as a test that gets no data.

This happened on #1461. pip stopped with a dependency conflict:

ERROR: Cannot install -r requirements.txt (line 2) and opentelemetry-api==1.45.1 because these package versions have conflicting dependencies.

The job then printed "otlp-python built successfully", with only lambda_function.py in the package. Later, the otlp integration suite failed because the Python function sent no trace.

Cause

The script sets set -e, but the build loop calls the build function inside an if condition. Bash turns off set -e in that context, so the script continues after pip fails. The check after the install step looks only for a non-empty package/ directory, and the script copies the .py files into that directory first. So the check always passes.

This PR

Checks the exit status of the docker run step that runs pip. When that step fails, the function prints the exit status and returns 1. The job then fails and lists the function. The message names the docker run step, not pip, because Docker can also fail before pip starts. An example is a Docker daemon that is not running.

Testing

Steps

1. Put a test function with conflicting requirements in a copy of the script layout.
2. Replaced docker on the PATH with a stub that exits 1, and ran the script from main and from this branch.
3. Replaced the stub with one that exits 125, and ran this branch again.
4. Replaced the stub with one that writes a file to package/ and exits 0, and ran this branch again.

Result

Case	Exit code before	Exit code after
pip fails	0, "All Python Lambda builds completed successfully!"	1, "Build failed: docker run ... pip install exited with status 1"
Docker exits 125	Not run	1, "Build failed: docker run ... pip install exited with status 125"
pip passes	Not run	0

I did not run the real Docker image. CI runs it.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-02T19:29:45.744507Z	86e7aef	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Copilot]

🟡 Changes recommended

The script reports Docker startup failures as pip errors, which can misdirect troubleshooting.

1 open issue

• Report Docker command failures separately from pip errors · New

What changed in this PR

This PR makes Python integration-test Lambda builds fail when dependency installation fails, preventing incomplete packages from causing misleading downstream test failures.

Changes:

• Explicitly checks the Docker command’s exit status rather than relying on set -e.
• Reports installation failure and returns a nonzero status to the build loop.
• Documents why the existing package-directory check cannot detect pip failures.

File	Description
integration-tests/​scripts/​build-python.sh	Adds explicit failure handling around Docker-based dependency installation.

_{Review effort: Balanced}

[datadog-official]

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 72f39db | Docs | Give us feedback!}