Bug#881739: marked as done (benchmark: FTBFS on hurd-i386: clock_gettime(CLOCK_THREAD_CPUTIME_ID, ...) failed)

[Debian Bug Tracking System]

Your message dated Sat, 10 Jan 2026 17:23:47 +0100
with message-id <aWJ9E6eowkIw_KUY at end>
and subject line Re: Bug#881739: benchmark: FTBFS on hurd-i386: clock_gettime(CLOCK_THREAD_CPUTIME_ID, ...) failed
has caused the Debian Bug report #881739,
regarding benchmark: FTBFS on hurd-i386: clock_gettime(CLOCK_THREAD_CPUTIME_ID, ...) failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner at bugs.debian.org
immediately.)


-- 
881739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881739
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: "Aaron M. Ucko" <ucko at debian.org>
Subject: benchmark: FTBFS on hurd-i386: clock_gettime(CLOCK_THREAD_CPUTIME_ID, ...) failed
Date: Tue, 14 Nov 2017 11:24:55 -0500
Size: 3917
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20260110/48b8ba3e/attachment-0002.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Samuel Thibault <sthibault at debian.org>
Subject: Re: Bug#881739: benchmark: FTBFS on hurd-i386: clock_gettime(CLOCK_THREAD_CPUTIME_ID, ...) failed
Date: Sat, 10 Jan 2026 17:23:47 +0100
Size: 3265
URL: <http://alioth-lists.debian.net/pipermail/debian-science-maintainers/attachments/20260110/48b8ba3e/attachment-0003.eml>