On Thu, 2022-11-24 at 07:40 +0100, Jean Abou Samra wrote:
> Le 23/11/2022 à 23:47, Jonas Hahnfeld a écrit :
>
> > https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00272.html
> > (which is finally a crash that I can reproduce) seems to be solved
> > by the current tip of the
> Le 24/11/2022 15:10 CET, Kevin Barry a écrit :
>
>
> On Thu, Nov 24, 2022 at 02:58:16PM +0100, Jean Abou Samra wrote:
> > What would be the difference with 'make doc'?
> I was referring to the kind of scores used to test/reproduce the
> heisenbug we had on Windows, i.e. designed to trigger
On Thu, Nov 24, 2022 at 02:58:16PM +0100, Jean Abou Samra wrote:
> What would be the difference with 'make doc'?
I was referring to the kind of scores used to test/reproduce the
heisenbug we had on Windows, i.e. designed to trigger GC-related
problems. Would it be worth saving some scores like
> Le 24/11/2022 14:05 CET, Kevin Barry a écrit :
>
>
> On Thu, Nov 24, 2022 at 12:26:57PM +0100, Jean Abou Samra wrote:
> > Le 24/11/2022 à 12:12, Kevin Barry a écrit :
> >
> > GC is definitely not the kind of thing where "passes the
> > regtests" means there is no problem. As we have seen
On Thu, Nov 24, 2022 at 12:26:57PM +0100, Jean Abou Samra wrote:
> Le 24/11/2022 à 12:12, Kevin Barry a écrit :
>
> GC is definitely not the kind of thing where "passes the
> regtests" means there is no problem. As we have seen in the
> past, the most infuriating and mysterious GC problems
Le 24/11/2022 à 12:12, Kevin Barry a écrit :
To practically answer your question: I don't think there's much we can
do: we are more or less at the mercy of the Guile project.
Yup.
I'm tempted to suggest we add some tests that might catch breaking changes to
Guile's GC, but of course our
On Thu, Nov 24, 2022 at 03:37:43AM +0100, Jean Abou Samra wrote:
> Had anyone seen this??
No, but it's not surprising: Guile sometimes seems to be a one-person
hobby project. It's not a project that cares much about breaking things
for its users.
> https://github.com/wingo/whippet-gc
>
> This
