Skip to content

Allow the XLSForm new_feature question geometry type to be configurable #554

Allow the XLSForm new_feature question geometry type to be configurable

Allow the XLSForm new_feature question geometry type to be configurable #554

Triggered via pull request January 10, 2025 15:08
Status Failure
Total duration 4m 21s
Artifacts 1

pytest.yml

on: pull_request
pytest  /  check-img-cache
4s
pytest / check-img-cache
pytest  /  ...  /  build-image
1m 45s
pytest / test-img-build / build-image
pytest  /  ...  /  scan-image
0s
pytest / test-img-build / scan-image
Fit to window
Zoom out
Zoom in

Annotations

1 error and 6 warnings
pytest / run-tests
Process completed with exit code 1.
pytest / check-img-cache
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
pytest / test-img-build / build-image
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
Legacy key/value format with whitespace separator should not be used: Dockerfile#L36
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L37
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
Legacy key/value format with whitespace separator should not be used: Dockerfile#L38
LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format More info: https://docs.docker.com/go/dockerfile/rule/legacy-key-value-format/
pytest / run-tests
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Artifacts

Produced during runtime
Name Size
hotosm~osm-fieldwork~8SOMYA.dockerbuild
101 KB