mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-14 04:39:33 +00:00
f95276bfaf
In setup, write a containers.conf.d file with db_backend
as specified in .cirrus.yml.
This is actually much scarier and more achy-breaky than
merely "sqlite system tests": it enables sqlite in e2e
tests. ("But wait, we already do that!" -- no, not really.
sqlite in e2e is being done via --db-backend option, and
some podman commands in e2e do not use the standard options.
See #17904.
This is unlikely to get merged any time soon (March, maybe
even April) because sqlite is still too fragile; this will
trigger more flakes than are currently acceptable. Also,
the nasty auto-update flake seems to trigger much more
reliably with sqlite. We need that one fixed.
Signed-off-by: Ed Santiago <santiago@redhat.com>
|
||
|---|---|---|
| .. | ||
| 99-do-not-use-google-subnets.conflist | ||
| check_go_changes.sh | ||
| CIModes.md | ||
| cirrus_yaml_test.py | ||
| lib.sh | ||
| lib.sh.t | ||
| logcollector.sh | ||
| logformatter | ||
| logformatter.t | ||
| postbuild.sh | ||
| pr-removes-fixed-skips | ||
| pr-removes-fixed-skips.t | ||
| pr-should-include-tests | ||
| pr-should-include-tests.t | ||
| prebuild.sh | ||
| required_host_ports.txt | ||
| runner.sh | ||
| setup_environment.sh | ||
| swagger_stack_trace.png | ||
| timestamp.awk | ||
| win-installer-install.ps1 | ||
| win-installer-main.ps1 | ||
| win-podman-machine-main.ps1 | ||
| win-podman-machine-verify.ps1 | ||
| wsl-env-launch.ps1 | ||
