3740bb81c5
Some checks failed
build-and-release / build (employees) (push) Successful in 18s
build-and-release / build (cron) (push) Successful in 23s
build-and-release / build (gateway) (push) Successful in 9s
build-and-release / build (graphic-designers) (push) Successful in 8s
build-and-release / build (catering-services) (push) Successful in 1m38s
build-and-release / build (jobs) (push) Successful in 9s
build-and-release / build (fitness-trainers) (push) Successful in 1m29s
build-and-release / build (payments) (push) Successful in 9s
build-and-release / build (photographers) (push) Successful in 11s
build-and-release / build (companies) (push) Successful in 2m15s
build-and-release / build (customers) (push) Successful in 2m26s
build-and-release / build (tutors) (push) Successful in 18s
build-and-release / build (developers) (push) Successful in 2m48s
build-and-release / build (video-editors) (push) Successful in 18s
backend-integration-tests / ai-credits (push) Failing after 10s
build-and-release / build (job-seekers) (push) Successful in 2m48s
build-and-release / build (makeup-artists) (push) Successful in 2m0s
build-and-release / build (users) (push) Has been cancelled
build-and-release / build (social-media-managers) (push) Has been cancelled
build-and-release / build (ugc-content-creators) (push) Has been cancelled
Previous job died silently right after checkout with no logs at all from the 'Check for relevant changes' step onward - shallow clone (default fetch-depth:1, unlike build.yaml which sets fetch-depth:0) may have been the cause. Matching build.yaml's checkout config. Also re-set TEST_DATABASE_URL with a properly percent-encoded password (the raw '@' in it made the postgresql:// URI ambiguous to parse). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build.yaml | ||
| test.yaml | ||