Your message dated Tue, 05 Mar 2024 12:51:11 +0000
with message-id <eebfbc5a275dd1aa2c82588129910...@riseup.net>
and subject line Re:  jruby-utils-clojure: FTBFS: E: Build killed with signal 
TERM after 150 minutes of inactivity
has caused the Debian Bug report #1042031,
regarding jruby-utils-clojure: FTBFS: E: Build killed with signal TERM after 
150 minutes of inactivity
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 ow...@bugs.debian.org
immediately.)


-- 
1042031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jruby-utils-clojure
Version: 4.0.3-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230724 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> expected: nil
>   actual: org.jruby.exceptions.NoMethodError: (NoMethodError) undefined 
> method `load_defaults' for Gem::Specification:Class
>  at RUBY.<main> (/usr/share/jruby/lib/ruby/stdlib/rubygems.rb:1338)
>     org.jruby.RubyKernel.require (org/jruby/RubyKernel.java:1017)
>     RUBY.<main> (uri:classloader:/jruby/kernel/gem_prelude.rb:3)
>     org.jruby.RubyKernel.load (org/jruby/RubyKernel.java:1052)
>     RUBY.<main> (file:/usr/share/java/jruby-base.jar!/jruby/preludes.rb:4)
> 
> lein test puppetlabs.services.jruby-pool-manager.jruby-locking-test
> 
> lein test :only 
> puppetlabs.services.jruby-pool-manager.jruby-locking-test/with-lock-with-timeout-test
> 
> ERROR in (with-lock-with-timeout-test) (JRubyPool.java:368)
> Uncaught exception, not in assertion.
> expected: nil
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2023/07/24/jruby-utils-clojure_4.0.3-4_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230724;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230724&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

--- End Message ---
--- Begin Message ---
Version: 5.1.0-2

Hello,

I believe this bug is now fixed in the latest version of the package
(and JRuby) in sid.

Thanks,

-- Jérôme

--- End Message ---

Reply via email to