|
| 1 | +#!/bin/bash |
| 2 | +# -*- indent-tabs-mode: nil; tab-width: 2; sh-indentation: 2; -*- |
| 3 | + |
| 4 | +# Test --test-mode: build failure without prebuilt fallback |
| 5 | +# |
| 6 | +# Verifies that when a package fails to build and no prebuilt wheel is available |
| 7 | +# (because the package is not on PyPI), test-mode records the failure. |
| 8 | +# Uses a local git repo fixture with a broken build backend. |
| 9 | +# |
| 10 | +# See: https://github.com/python-wheel-build/fromager/issues/895 |
| 11 | + |
| 12 | +SCRIPTDIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )" |
| 13 | +source "$SCRIPTDIR/common.sh" |
| 14 | + |
| 15 | +# Use the test_build_failure fixture (local git repo) |
| 16 | +# Initialize git repo at runtime (fixture files are committed without .git) |
| 17 | +FIXTURE_DIR="$SCRIPTDIR/test_build_failure" |
| 18 | +CREATED_FIXTURE_GIT=false |
| 19 | +if [ ! -d "$FIXTURE_DIR/.git" ]; then |
| 20 | + CREATED_FIXTURE_GIT=true |
| 21 | + (cd "$FIXTURE_DIR" && git init -q && \ |
| 22 | + git config user.email "test@example.com" && \ |
| 23 | + git config user.name "Test User" && \ |
| 24 | + git add -A && git commit -q -m "init") |
| 25 | +fi |
| 26 | +FIXTURE_URL="git+file://${FIXTURE_DIR}" |
| 27 | + |
| 28 | +# Cleanup .git on exit if we created it (prevents flaky reruns) |
| 29 | +cleanup_fixture_git() { |
| 30 | + if [ "$CREATED_FIXTURE_GIT" = true ] && [ -d "$FIXTURE_DIR/.git" ]; then |
| 31 | + rm -rf "$FIXTURE_DIR/.git" |
| 32 | + fi |
| 33 | +} |
| 34 | +trap cleanup_fixture_git EXIT |
| 35 | + |
| 36 | +# Create a requirements file pointing to the local fixture |
| 37 | +REQUIREMENTS_FILE="$OUTDIR/test-requirements.txt" |
| 38 | +echo "test_build_failure @ ${FIXTURE_URL}" > "$REQUIREMENTS_FILE" |
| 39 | + |
| 40 | +# Run bootstrap in test mode |
| 41 | +# - Package resolves from local git repo |
| 42 | +# - Build fails (broken build backend) |
| 43 | +# - Prebuilt fallback fails (package not on PyPI) |
| 44 | +# - Failure should be recorded |
| 45 | +set +e |
| 46 | +fromager \ |
| 47 | + --log-file="$OUTDIR/bootstrap.log" \ |
| 48 | + --error-log-file="$OUTDIR/fromager-errors.log" \ |
| 49 | + --sdists-repo="$OUTDIR/sdists-repo" \ |
| 50 | + --wheels-repo="$OUTDIR/wheels-repo" \ |
| 51 | + --work-dir="$OUTDIR/work-dir" \ |
| 52 | + bootstrap --test-mode -r "$REQUIREMENTS_FILE" |
| 53 | +EXIT_CODE=$? |
| 54 | +set -e |
| 55 | + |
| 56 | +pass=true |
| 57 | + |
| 58 | +# Check 1: Exit code should be 1 (failures recorded) |
| 59 | +if [ "$EXIT_CODE" -ne 1 ]; then |
| 60 | + echo "FAIL: Expected exit code 1, got $EXIT_CODE" 1>&2 |
| 61 | + pass=false |
| 62 | +fi |
| 63 | + |
| 64 | +# Check 2: The test-mode-failures JSON file should exist |
| 65 | +FAILURES_FILE=$(find "$OUTDIR/work-dir" -name "test-mode-failures-*.json" 2>/dev/null | head -1) |
| 66 | +if [ -z "$FAILURES_FILE" ] || [ ! -f "$FAILURES_FILE" ]; then |
| 67 | + echo "FAIL: test-mode-failures-*.json file not found" 1>&2 |
| 68 | + pass=false |
| 69 | +else |
| 70 | + echo "Found failures file: $FAILURES_FILE" |
| 71 | + |
| 72 | + # Check 3: test_build_failure should be in failed packages |
| 73 | + # Note: package name uses underscore as recorded by fromager |
| 74 | + if ! jq -e '.failures[] | select(.package == "test_build_failure")' "$FAILURES_FILE" > /dev/null 2>&1; then |
| 75 | + echo "FAIL: Expected 'test_build_failure' in failed packages" 1>&2 |
| 76 | + jq '.' "$FAILURES_FILE" 1>&2 |
| 77 | + pass=false |
| 78 | + fi |
| 79 | + |
| 80 | + # Check 4: failure_type MUST be 'bootstrap' (actual build failure, not resolution) |
| 81 | + # Pinning to 'bootstrap' catches regressions if fromager misclassifies failures |
| 82 | + FAILURE_TYPE=$(jq -r '[.failures[] | select(.package == "test_build_failure")][0].failure_type' "$FAILURES_FILE") |
| 83 | + if [ "$FAILURE_TYPE" != "bootstrap" ]; then |
| 84 | + echo "FAIL: Expected failure_type 'bootstrap', got '$FAILURE_TYPE'" 1>&2 |
| 85 | + pass=false |
| 86 | + else |
| 87 | + echo "Failure type: $FAILURE_TYPE" |
| 88 | + fi |
| 89 | + |
| 90 | + # Check 5: exception_message should indicate a build-related error |
| 91 | + EXCEPTION_MSG=$(jq -r '[.failures[] | select(.package == "test_build_failure")][0].exception_message' "$FAILURES_FILE") |
| 92 | + if [[ "$EXCEPTION_MSG" != *"nonexistent_file"* ]] && [[ "$EXCEPTION_MSG" != *"MANIFEST"* ]] && [[ "$EXCEPTION_MSG" != *"build"* ]] && [[ "$EXCEPTION_MSG" != *"CalledProcessError"* ]]; then |
| 93 | + echo "FAIL: Expected exception message about build failure, got: $EXCEPTION_MSG" 1>&2 |
| 94 | + pass=false |
| 95 | + fi |
| 96 | +fi |
| 97 | + |
| 98 | +# Check 6: Log should show test mode enabled |
| 99 | +if ! grep -q "test mode enabled" "$OUTDIR/bootstrap.log"; then |
| 100 | + echo "FAIL: Log should contain 'test mode enabled'" 1>&2 |
| 101 | + pass=false |
| 102 | +fi |
| 103 | + |
| 104 | +# Check 7: Log may show fallback attempt (depends on where failure occurs) |
| 105 | +# Note: Fallback is only attempted when build fails after resolution succeeds. |
| 106 | +# Our fixture fails during metadata extraction, so fallback may not be triggered. |
| 107 | +if grep -q "pre-built fallback" "$OUTDIR/bootstrap.log"; then |
| 108 | + echo "INFO: Fallback was attempted (package not on PyPI, so it failed)" |
| 109 | +else |
| 110 | + echo "INFO: No fallback attempt (failure occurred before build phase)" |
| 111 | +fi |
| 112 | + |
| 113 | +$pass |
0 commit comments