Skip to content
Unit tests

Add option to log warning when placeholder values is missing when templating #20176

Sign in to view logs

Add option to log warning when placeholder values is missing when templating

Add option to log warning when placeholder values is missing when templating #20176

Triggered via pull request February 24, 2025 05:17
@desertaxledesertaxle
synchronize #17261
warn-on-templating-notset
Status Failure
Total duration 2m 36s
Artifacts –

python-tests.yaml

on: pull_request
typesafety
39s
typesafety
Matrix: run-docker-tests
Matrix: run-tests
Fit to window
Zoom out
Zoom in

Annotations

29 errors
Database and Orchestration Tests - python:3.11, sqlite
Process completed with exit code 4.
typesafety
Process completed with exit code 4.
Server Tests - python:3.12, sqlite
Process completed with exit code 4.
Database and Orchestration Tests - python:3.10, sqlite
Process completed with exit code 4.
Server Tests - python:3.9, sqlite
Process completed with exit code 4.
Database and Orchestration Tests - python:3.12, sqlite
Process completed with exit code 4.
Database and Orchestration Tests - python:3.9, sqlite
Process completed with exit code 4.
Server Tests - python:3.11, sqlite
Process completed with exit code 4.
Server Tests - python:3.10, sqlite
Process completed with exit code 4.
Database and Orchestration Tests - python:3.12, postgres:14
Process completed with exit code 4.
Runner, Worker, Settings, Input, and CLI Tests - python:3.11, postgres:14
Process completed with exit code 4.
Server Tests - python:3.11, postgres:14
Process completed with exit code 4.
Database and Orchestration Tests - python:3.10, postgres:14
Process completed with exit code 4.
Database and Orchestration Tests - python:3.11, postgres:14
Process completed with exit code 4.
Server Tests - python:3.10, postgres:14
Process completed with exit code 4.
Client Tests - python:3.9, postgres:14
Process completed with exit code 4.
Database and Orchestration Tests - python:3.9, postgres:14
Process completed with exit code 4.
Runner, Worker, Settings, Input, and CLI Tests - python:3.12, postgres:14
Process completed with exit code 4.
Client Tests - python:3.11, postgres:14
Process completed with exit code 4.
Client Tests - python:3.10, postgres:14
Process completed with exit code 4.
Server Tests - python:3.12, postgres:14
Process completed with exit code 4.
Client Tests - python:3.12, postgres:14
Process completed with exit code 4.
Server Tests - python:3.9, postgres:14
Process completed with exit code 4.
Runner, Worker, Settings, Input, and CLI Tests - python:3.9, postgres:14
Process completed with exit code 4.
Runner, Worker, Settings, Input, and CLI Tests - python:3.10, postgres:14
Process completed with exit code 4.
docker, python:3.12
buildx failed with: ERROR: failed to solve: process "/bin/sh -c prefect version" did not complete successfully: exit code: 1
docker, python:3.10
buildx failed with: ERROR: failed to solve: process "/bin/sh -c prefect version" did not complete successfully: exit code: 1
docker, python:3.11
buildx failed with: ERROR: failed to solve: process "/bin/sh -c prefect version" did not complete successfully: exit code: 1
docker, python:3.9
buildx failed with: ERROR: failed to solve: process "/bin/sh -c prefect version" did not complete successfully: exit code: 1