12007530642
78%
master: 80%

Ran 25 Nov 2024 09:58AM UTC

Jobs 1

Files 37

Run time 1min

Badge

Embed ▾

Committed 25 Nov 2024 09:57AM UTC coverage: 78.273%. Remained the same

Build # 12007530642

Build Type

push

github

Committed by

web-flow

Commit Message

CP-51692: use Event.from instead of Event.next (#6125)

Event.next can lose events, and we try to encourage our API users to
always use Event.from instead.

My understanding (which could be wrong) is that Event.from will give you
the events since a given point in time (token), whereas Event.next only
gives you even from when you called the API (missing events between API
calls).

This PR introduces a feature flag that we can use to switch the interal
users of Event.next to Event.from.
Doing so I've discovered a bug in ocaml-rpc, where `int32_of_rpc`
doesn't accept Int32 as input, just Int.
There is a workaround here for now, but I intend to fix this upstream
instead, hence the draft PR.

Run Details

3462 of 4423 relevant lines covered (78.27%)

0.78 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	python3.11 - 12007530642.1	25 Nov 2024 09:58AM UTC	37	78.27	GitHub Action Run

xapi-project / xen-api / 12007530642
78%
master: 80%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 12007530642

xapi-project / xen-api / 12007530642 78% master: 80%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 12007530642

xapi-project / xen-api / 12007530642
78%
master: 80%

README BADGES
x