Hi Carlo,
Carlo Zancanaro skribis:
> When the next release of the Shepherd is made (including commit
> 9ec5ce9a45441417a6ee4138cdcbf1b1f2b2) we should have the
> capability to resolve this ticket.
Woohoo!
I’d like to make sure we understand the story with ‘EINTR-safe’, but
after that I’m h
On Sat, Sep 01 2018, Carlo Zancanaro wrote:
I'll send through an updated patch once I've cleaned it up a
bit, [ ... ]
Updated patch attached.
From 47647b767930d16ab5a3b855993daf6ddf98f230 Mon Sep 17 00:00:00 2001
From: Carlo Zancanaro
Date: Sun, 26 Aug 2018 21:54:14 +1000
Subject: [PATCH] gnu
Hey Ludo’,
On Sat, Sep 01 2018, Ludovic Courtès wrote:
I’d like to make sure we understand the story with ‘EINTR-safe’,
but after that I’m happy to push a release.
Do you have any thoughts about why it could be failing, or things
I could investigate? I don't know where to start.
One possibl
Heya,
Carlo Zancanaro skribis:
> On Sat, Sep 01 2018, Ludovic Courtès wrote:
>> I’d like to make sure we understand the story with ‘EINTR-safe’, but
>> after that I’m happy to push a release.
>
> Do you have any thoughts about why it could be failing, or things I
> could investigate? I don't kno
Clément Lassieur writes:
> Reported by Ludovic on IRC.
>
> Some builds are marked as failed, but they were never built. Plus,
> starttime and stoptime don't make sense.
>
> --8<---cut here---start->8---
> snape: i just noticed something fishy:
> https
On Sun, Sep 02 2018, Ludovic Courtès wrote:
First, could you check (in a VM) whether the boot failure is
reproducible when that patch that removes ‘EINTR-safe’ is
applied?
As far as I can tell it's completely reproducible.
If it’s 100% reproducible, could you share the VM’s output?
Sure.
