Hi Etienne,
I've uploaded a new version: 4.0-beta16. It should address the errors
that were found. The errors only occurred when running multiple
instances of bali-phy at once immediately after installing a new
version, which rarely occurred except when running tests with ninja.
I've added a few layers of safeguards around reading/writing cached data
structures to prevent this from happening again.
I've added `ninja test` to the CI, in addition to the non-ninja test
harness, to prevent surprises like this in the future.
If you can try packaging 4.0-beta16 that would be great. There
shouldn't be any errors, but if any occur, I'll try to make a beta17
relatively quickly.
-BenRI
On 7/10/24 9:02 AM, Étienne Mollier wrote:
Hi again,
Étienne Mollier, on 2024-07-10:
Full log would probably be better suited in your issue tracker
than in a mailing list. Let me know if you need it. I tried to
trip Salsa CI so it produces an independent build and a build
log to point to, but it doesn't look to be operating right now.
Actually, the CI kicked in and reported a different set of test
failures[1]. I'm not sure what's up. Does this ring a bell?
[1]: https://salsa.debian.org/med-team/bali-phy/-/jobs/5952519
Have a nice day, :)
