18654091439
80%
master: 80%

Ran 20 Oct 2025 01:48PM UTC

Jobs 1

Files 34

Run time 1min

Badge

Embed ▾

Committed 20 Oct 2025 01:46PM UTC coverage: 80.368%. Remained the same

Build # 18654091439

Build Type

push

github

Committed by

web-flow

Commit Message

RFC: update better VM revert proposal  (#6696)

This proposal is 11 years old and the architecture of xapi has changed
enough that the proposal needs changing.

In particular, SMAPIv3 has been introduced which means that there's an
xapi storage interface shared between the two SMAPI backend, and that
the fallback the logic that was done at SMAPI level now must be done at
the
level of xapi.

I've also elected to further restrict the fallback behaviour to VM
reverts, VDI revert will require backend support: it reduces the chances
of
failures during revert resulting in wrong fields in the database.

I'm still unsure about exposing VDI.revert, I would avoid it if at all
possible, maybe as an internal or hidden API? It might be useful to
exposed to use it in quicktests, like it was done in the initial
prototype.

Run Details

3496 of 4350 relevant lines covered (80.37%)

0.8 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	python3.11 - 18654091439.1	20 Oct 2025 01:48PM UTC	34	80.37	GitHub Action Run

xapi-project / xen-api / 18654091439
80%
master: 80%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 18654091439

xapi-project / xen-api / 18654091439 80% master: 80%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 18654091439

xapi-project / xen-api / 18654091439
80%
master: 80%

README BADGES
x