Make reporting more metrics for tasks possible #758
Triggered via pull request
February 14, 2025 15:47
mateka
Status
Success
Total duration
15m 44s
Artifacts
–
pythonbuild.yml
on: pull_request
Matrix: base
Matrix: core
Matrix: postgres
Annotations
97 warnings
|
base (3.10, flake8)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.10, flake8)
Cache not found for keys: Linux-pip-
|
|
base (3.10, docs)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.10, docs)
Cache not found for keys: Linux-pip-
|
|
base (3.10, docs)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.8, py38-apache)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.8, py38-apache)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.8, py38-apache)
Cache not found for keys: Linux-pip-
|
|
base (3.10, py310-azureblob)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.10, py310-azureblob)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.10, py310-azureblob)
Cache not found for keys: Linux-pip-
|
|
base (3.8, py38-azureblob)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.8, py38-azureblob)
Cache not found for keys: Linux-pip-
|
|
base (3.8, py38-azureblob)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.9, py39-azureblob)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.9, py39-azureblob)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.9, py39-azureblob)
Cache not found for keys: Linux-pip-
|
|
base (3.10, py310-apache)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.10, py310-apache)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.10, py310-apache)
Cache not found for keys: Linux-pip-
|
|
base (3.9, py39-apache)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.9, py39-apache)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.9, py39-apache)
Cache not found for keys: Linux-pip-
|
|
base (3.11, py311-azureblob)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.11, py311-azureblob)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.11, py311-azureblob)
Cache not found for keys: Linux-pip-
|
|
postgres (3.8, py38-postgres)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.8, py38-aws)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.8, py38-aws)
Cache not found for keys: Linux-pip-
|
|
base (3.8, py38-aws)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.11, py311-apache)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.11, py311-apache)
Cache not found for keys: Linux-pip-
|
|
base (3.11, py311-apache)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
postgres (3.9, py39-postgres)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.10, py310-aws)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.10, py310-aws)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.10, py310-aws)
Cache not found for keys: Linux-pip-
|
|
postgres (3.10, py310-postgres)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.7, py37-azureblob)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.7, py37-azureblob)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.7, py37-azureblob)
Cache not found for keys: Linux-pip-
|
|
base (3.7, py37-apache)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.7, py37-apache)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.7, py37-apache)
Cache not found for keys: Linux-pip-
|
|
postgres (3.11, py311-postgres)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.8, py38-unixsocket, true)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.8, py38-unixsocket, true)
Cache not found for keys: Linux-pip-
|
|
base (3.8, py38-unixsocket, true)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.9, py39-unixsocket, true)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.9, py39-unixsocket, true)
Cache not found for keys: Linux-pip-
|
|
base (3.9, py39-unixsocket, true)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.12, py312-azureblob)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.12, py312-azureblob)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.12, py312-azureblob)
Cache not found for keys: Linux-pip-
|
|
postgres (3.7, py37-postgres)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.11, py311-unixsocket, true)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.11, py311-unixsocket, true)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.11, py311-unixsocket, true)
Cache not found for keys: Linux-pip-
|
|
base (3.12, py312-apache)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.12, py312-apache)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.12, py312-apache)
Cache not found for keys: Linux-pip-
|
|
base (3.7, py37-aws)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.7, py37-aws)
Cache not found for keys: Linux-pip-
|
|
base (3.7, py37-aws)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
postgres (3.12, py312-postgres)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.11, py311-aws)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.11, py311-aws)
Cache not found for keys: Linux-pip-
|
|
base (3.11, py311-aws)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.7, py37-unixsocket, true)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.7, py37-unixsocket, true)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.7, py37-unixsocket, true)
Cache not found for keys: Linux-pip-
|
|
base (3.9, py39-aws)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.9, py39-aws)
Cache not found for keys: Linux-pip-
|
|
base (3.9, py39-aws)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.10, py310-unixsocket, true)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.10, py310-unixsocket, true)
Cache not found for keys: Linux-pip-
|
|
base (3.10, py310-unixsocket, true)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
core (3.9, py39-core)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
core (3.9, py39-core)
Cache not found for keys: Linux-pip-
|
|
core (3.9, py39-core)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
core (3.8, py38-core)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
core (3.8, py38-core)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
core (3.8, py38-core)
Cache not found for keys: Linux-pip-
|
|
base (3.12, py312-aws)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.12, py312-aws)
Cache not found for keys: Linux-pip-
|
|
base (3.12, py312-aws)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
core (3.7, py37-core)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
core (3.7, py37-core)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
core (3.7, py37-core)
Cache not found for keys: Linux-pip-
|
|
base (3.12, py312-unixsocket, true)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
base (3.12, py312-unixsocket, true)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
base (3.12, py312-unixsocket, true)
Cache not found for keys: Linux-pip-
|
|
core (3.10, py310-core)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
core (3.11, py311-core)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|
|
core (3.11, py311-core)
Cache not found for keys: Linux-pip-
|
|
core (3.11, py311-core)
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
|
|
core (3.12, py312-core)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
|