GNU bug report logs - #37037
Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing test.

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37037 in the body.
You can then email your comments to 37037 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Svante Signell <svante.signell <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing test.
Date: Thu, 15 Aug 2019 14:29:07 +0200

Hello,

When building Debian version 2.0.13+1-5.1 one test fails making the
whole build to fail. The problem is in the file test-
suite/tests/statprof.test. According to that file it is known that
ITIMER_PROF is not implemented:

;; Throw `unresolved' upon ENOSYS.  This is used to skip tests on
;; platforms such as GNU/Hurd where `ITIMER_PROF' is is currently
;; unimplemented.
      
(define-syntax-rule (when-implemented body ...)
  (catch 'system-error
    (lambda ()
      body ...)
    (lambda args
      (let ((errno (system-error-errno args)))
        (false-if-exception (statprof-stop))
        (if (= errno ENOSYS)
            (throw 'unresolved)
            (apply throw args))))))

(pass-if-equal "return values"
    '(42 77)
  (call-with-values
      (lambda ()
        (with-output-to-port (%make-void-port "w")
          (lambda ()
            (with-statprof
                (let loop ((i 10000))
                  (if (zero? i)
                      (values 42 77)
                      (loop (1- i))))))))
    list))

However, when that test is run the following is reported:

Running statprof.test
ERROR: statprof.test: return values - arguments: ((system-error
"setitimer" "~A" ("Function not implemented") (1073741902)))
ERROR: statprof.test: statistical sample counts within expected range -
arguments: ((misc-error #f "~A" ("Can't reset profiler while profiler
is running.") #f))
ERROR: statprof.test: accurate call counting - arguments: ((misc-error
#f "~A" ("Can't reset profiler while profiler is running.") #f))

making that test (and package build) to fail.

An UNRESOLVED result would make that test to enable a successful
package build. Unfortunately I don't know anything about scheme code so
I cannot propose a patch to the Debian package maintainer. Maybe you
can help me?

Please Cc: since I'm not subscribed.

Thanks!

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Svante Signell <svante.signell <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: Re: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing test.
Date: Thu, 22 Aug 2019 20:33:28 +0200

Ping!

On Thu, 2019-08-15 at 14:29 +0200, Svante Signell wrote:
> Hello,
> 
> When building Debian version 2.0.13+1-5.1 one test fails making the
> whole build to fail. The problem is in the file test-
> suite/tests/statprof.test. According to that file it is known that
> ITIMER_PROF is not implemented:
> 
> ;; Throw `unresolved' upon ENOSYS.  This is used to skip tests on
> ;; platforms such as GNU/Hurd where `ITIMER_PROF' is is currently
> ;; unimplemented.
>       
> (define-syntax-rule (when-implemented body ...)
>   (catch 'system-error
>     (lambda ()
>       body ...)
>     (lambda args
>       (let ((errno (system-error-errno args)))
>         (false-if-exception (statprof-stop))
>         (if (= errno ENOSYS)
>             (throw 'unresolved)
>             (apply throw args))))))
> 
> (pass-if-equal "return values"
>     '(42 77)
>   (call-with-values
>       (lambda ()
>         (with-output-to-port (%make-void-port "w")
>           (lambda ()
>             (with-statprof
>                 (let loop ((i 10000))
>                   (if (zero? i)
>                       (values 42 77)
>                       (loop (1- i))))))))
>     list))
> 
> However, when that test is run the following is reported:
> 
> Running statprof.test
> ERROR: statprof.test: return values - arguments: ((system-error
> "setitimer" "~A" ("Function not implemented") (1073741902)))
> ERROR: statprof.test: statistical sample counts within expected range
> -
> arguments: ((misc-error #f "~A" ("Can't reset profiler while profiler
> is running.") #f))
> ERROR: statprof.test: accurate call counting - arguments: ((misc-
> error
> #f "~A" ("Can't reset profiler while profiler is running.") #f))
> 
> making that test (and package build) to fail.
> 
> An UNRESOLVED result would make that test to enable a successful
> package build. Unfortunately I don't know anything about scheme code
> so
> I cannot propose a patch to the Debian package maintainer. Maybe you
> can help me?
> 
> Please Cc: since I'm not subscribed.
> 
> Thanks!
> 
> 

Message #11 received at 37037 <at> debbugs.gnu.org (full text, mbox):

From: Svante Signell <svante.signell <at> gmail.com>
To: 37037 <at> debbugs.gnu.org
Subject: [Fwd: Re: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing
 test.]
Date: Thu, 22 Aug 2019 20:34:30 +0200

[Message part 1 (text/plain, inline)]

[Message part 2 (message/rfc822, inline)]

From: Svante Signell <svante.signell <at> gmail.com>
To: bug-guile <at> gnu.org
Subject: Re: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one failing test.
Date: Thu, 22 Aug 2019 20:33:28 +0200

Ping!

On Thu, 2019-08-15 at 14:29 +0200, Svante Signell wrote:
> Hello,
> 
> When building Debian version 2.0.13+1-5.1 one test fails making the
> whole build to fail. The problem is in the file test-
> suite/tests/statprof.test. According to that file it is known that
> ITIMER_PROF is not implemented:
> 
> ;; Throw `unresolved' upon ENOSYS.  This is used to skip tests on
> ;; platforms such as GNU/Hurd where `ITIMER_PROF' is is currently
> ;; unimplemented.
>       
> (define-syntax-rule (when-implemented body ...)
>   (catch 'system-error
>     (lambda ()
>       body ...)
>     (lambda args
>       (let ((errno (system-error-errno args)))
>         (false-if-exception (statprof-stop))
>         (if (= errno ENOSYS)
>             (throw 'unresolved)
>             (apply throw args))))))
> 
> (pass-if-equal "return values"
>     '(42 77)
>   (call-with-values
>       (lambda ()
>         (with-output-to-port (%make-void-port "w")
>           (lambda ()
>             (with-statprof
>                 (let loop ((i 10000))
>                   (if (zero? i)
>                       (values 42 77)
>                       (loop (1- i))))))))
>     list))
> 
> However, when that test is run the following is reported:
> 
> Running statprof.test
> ERROR: statprof.test: return values - arguments: ((system-error
> "setitimer" "~A" ("Function not implemented") (1073741902)))
> ERROR: statprof.test: statistical sample counts within expected range
> -
> arguments: ((misc-error #f "~A" ("Can't reset profiler while profiler
> is running.") #f))
> ERROR: statprof.test: accurate call counting - arguments: ((misc-
> error
> #f "~A" ("Can't reset profiler while profiler is running.") #f))
> 
> making that test (and package build) to fail.
> 
> An UNRESOLVED result would make that test to enable a successful
> package build. Unfortunately I don't know anything about scheme code
> so
> I cannot propose a patch to the Debian package maintainer. Maybe you
> can help me?
> 
> Please Cc: since I'm not subscribed.
> 
> Thanks!
> 
> 

Message #14 received at 37037 <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: Svante Signell <svante.signell <at> gmail.com>
Cc: 37037 <at> debbugs.gnu.org
Subject: Re: bug#37037: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one
 failing test.
Date: Thu, 22 Aug 2019 17:01:22 -0400

Hi Svante,

Svante Signell <svante.signell <at> gmail.com> writes:

> When building Debian version 2.0.13+1-5.1 one test fails making the
> whole build to fail. The problem is in the file test-
> suite/tests/statprof.test. According to that file it is known that
> ITIMER_PROF is not implemented:
>
> ;; Throw `unresolved' upon ENOSYS.  This is used to skip tests on
> ;; platforms such as GNU/Hurd where `ITIMER_PROF' is is currently
> ;; unimplemented.
>       
> (define-syntax-rule (when-implemented body ...)
>   (catch 'system-error
>     (lambda ()
>       body ...)
>     (lambda args
>       (let ((errno (system-error-errno args)))
>         (false-if-exception (statprof-stop))
>         (if (= errno ENOSYS)
>             (throw 'unresolved)
>             (apply throw args))))))
>
> (pass-if-equal "return values"
>     '(42 77)
>   (call-with-values
>       (lambda ()
>         (with-output-to-port (%make-void-port "w")
>           (lambda ()
>             (with-statprof
>                 (let loop ((i 10000))
>                   (if (zero? i)
>                       (values 42 77)
>                       (loop (1- i))))))))
>     list))

It looks like this issue was already fixed in Guile 2.0.14, by commit
f2764cb1031379c47a17c02fef3f8164a6ce9cda on the 'stable-2.0' branch:

  https://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.0&id=f2764cb1031379c47a17c02fef3f8164a6ce9cda

Would you like to try it and report back?

     Thanks,
       Mark

Message #17 received at 37037 <at> debbugs.gnu.org (full text, mbox):

From: Svante Signell <svante.signell <at> gmail.com>
To: Mark H Weaver <mhw <at> netris.org>
Cc: 37037 <at> debbugs.gnu.org
Subject: Re: bug#37037: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one
 failing test.
Date: Fri, 23 Aug 2019 13:16:46 +0200

On Thu, 2019-08-22 at 17:01 -0400, Mark H Weaver wrote:
> Hi Svante,
> 
> Svante Signell <svante.signell <at> gmail.com> writes:
> 
> It looks like this issue was already fixed in Guile 2.0.14, by commit
> f2764cb1031379c47a17c02fef3f8164a6ce9cda on the 'stable-2.0' branch:
> 
>   
> https://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.0&id=f2764cb1031379c47a17c02fef3f8164a6ce9cda
> 
> Would you like to try it and report back?

Thank you, that commit fixed the problem. Reported to Debian version
2.0.13+1-5.1 as bug #935505, see 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935505

Message #22 received at 37037-done <at> debbugs.gnu.org (full text, mbox):

From: Mark H Weaver <mhw <at> netris.org>
To: Svante Signell <svante.signell <at> gmail.com>
Cc: 37037-done <at> debbugs.gnu.org
Subject: Re: bug#37037: Guile 2.0.13+1-5.1 FTBFS on GNU/Hurd due to one
 failing test.
Date: Fri, 23 Aug 2019 15:23:21 -0400

Svante Signell <svante.signell <at> gmail.com> writes:

> On Thu, 2019-08-22 at 17:01 -0400, Mark H Weaver wrote:
>> It looks like this issue was already fixed in Guile 2.0.14, by commit
>> f2764cb1031379c47a17c02fef3f8164a6ce9cda on the 'stable-2.0' branch:
>>   
>> https://git.savannah.gnu.org/cgit/guile.git/commit/?h=stable-2.0&id=f2764cb1031379c47a17c02fef3f8164a6ce9cda
>> 
>> Would you like to try it and report back?
>
> Thank you, that commit fixed the problem. Reported to Debian version
> 2.0.13+1-5.1 as bug #935505, see 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935505

Great, thanks for letting us know.  I'm closing this bug now.

     Regards,
       Mark

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.