Skip to content
Python CI

Various fixes for targeting postgres in singularity (rebase) #2613

Sign in to view logs

Various fixes for targeting postgres in singularity (rebase)

Various fixes for targeting postgres in singularity (rebase) #2613

Triggered via pull request August 23, 2026 18:17
@jmchiltonjmchilton
synchronize #1679
jmchilton:postgres_singularity_fix_rebased
Status Failure
Total duration 5s
Artifacts –

ci.yaml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

13 errors
test (3.10, unit-quick)
The job was not started because your account is locked due to a billing issue.
test (3.13, unit-quick)
The job was not started because your account is locked due to a billing issue.
test (3.10, unit-nonredundant-noclientbuild-noshed-gx-dev)
The job was not started because your account is locked due to a billing issue.
test (3.13, lint)
The job was not started because your account is locked due to a billing issue.
test (3.10, unit-nonredundant-noclientbuild-noshed-nogx)
The job was not started because your account is locked due to a billing issue.
test (3.10, unit-nonredundant-noclientbuild-noshed-gx-231)
The job was not started because your account is locked due to a billing issue.
test (3.10, lint_docs)
The job was not started because your account is locked due to a billing issue.
test (3.10, mypy)
The job was not started because your account is locked due to a billing issue.
test (3.13, mypy)
The job was not started because your account is locked due to a billing issue.
test (3.10, lint)
The job was not started because your account is locked due to a billing issue.
test (3.10, unit-nonredundant-noclientbuild-noshed-gx-250)
The job was not started because your account is locked due to a billing issue.
test (3.10, unit-diagnostic-serveclientcmd)
The job was not started because your account is locked due to a billing issue.
test (3.10, unit-diagnostic-servebasic-gx-dev)
The job was not started because your account is locked due to a billing issue.