CI: enable sqlite system tests #17954
Conversation
openshift-ci
bot
added
release-note-none
do-not-merge/work-in-progress
openshift-ci
bot
added
the
approved
edsantiago
force-pushed
the
sqlite_containersconf
branch
2 times, most recently
from
c165b2e to
8b43963
Compare
|
heads-up, github CI reporting seems to be stalled. Job is done, all green, but as of the moment I write this github is still showing jobs queued. |
|
@cevich this job finished (green) many hours ago. Is there any way to tell Github to catch up, or do we have to resubmit all jobs? |
|
Whoa, that's weird. I don't remember ever seeing that behavior before. Looking at the timer, it's going on 6-hours, so I'd bet it will never be marked as completed. Since clearly they're all green, I would just ask for this to be manually merged. Unless you think re-running would be faster 😞 |
|
I don't mind repushing - this is a scary PR, and more testing is good. It's just, all PRs from this morning are stuck because of the github hiccup. I was wondering if there was a fix. |
edsantiago
force-pushed
the
sqlite_containersconf
branch
from
8b43963 to
678af68
Compare
|
Blocked by #17904 |
edsantiago
force-pushed
the
sqlite_containersconf
branch
4 times, most recently
from
d940c9f to
8d81445
Compare
edsantiago
force-pushed
the
sqlite_containersconf
branch
2 times, most recently
from
f01edea to
cd917d6
Compare
edsantiago
force-pushed
the
sqlite_containersconf
branch
3 times, most recently
from
5f4c1ca to
3204f99
Compare
edsantiago
force-pushed
the
sqlite_containersconf
branch
2 times, most recently
from
6cda2f3 to
fe5855f
Compare
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 containers#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 <[email protected]>
edsantiago
force-pushed
the
sqlite_containersconf
branch
from
fe5855f to
f95276b
Compare
edsantiago
changed the title
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
@cevich @containers/podman-maintainers this is ready to go. I hand-checked all logs, all flakes are the usual ones. |
openshift-ci
bot
added
the
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: edsantiago, vrothberg The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM |
|
/hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
github-actions
bot
added
the
locked - please file new issue/PR
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 [email protected]