ruby-ferret/0.11.8.7-2 in Jammy is behaving well on arm64:
https://autopkgtest.ubuntu.com/packages/ruby-ferret/jammy/arm64
** Changed in: ruby-ferret (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Since this seems to not be a blocker anymore I am lowering the
importance to low.
** Changed in: ruby-ferret (Ubuntu)
Importance: High => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804
The package started failing the same way on ppc64el in Impish:
https://autopkgtest.ubuntu.com/packages/r/ruby-ferret/impish/ppc64el
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804
Title:
** Merge proposal linked:
https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/402588
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804
Title:
DEP8 segfault on arm64
To
This test has not failed since Cosmic on armhf [1], so it is not a
blocker. Moreover, upstream is dead (more than 3 years with no new
commits), I submitted the patch I mentioned above and there is no answer
so far [2].
This package has no reverse dependencies, if it turns out a problem we
should
** Changed in: ruby2.5 (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804
Title:
DEP8 segfault on arm64
To manage notifications about this bug go to:
The error indeed takes a varying amount of runs to manifest itself.
- 13 runs
- 170 runs
- 62 runs
The 4th attempt is still running, and the count is at 309 currently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The error indeed takes a varying amount of runs to manifest itself.
- 13 runs
- 170 runs
- 62 runs
The 4th attempt is still running, and the count is at 309 currently.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Agreed, I had the same problem. This DEP-8 test doesn't fail in arm64
every time, on average it fails 2 out of 5 sequential executions for me.
It should happen because in some executions we are lucky and the memory
access is aligned. Applying the proposed patch I've not faced any
failure after
** Changed in: ruby-ferret (Ubuntu)
Assignee: (unassigned) => Lucas Kanashiro (lucaskanashiro)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804
Title:
DEP8 segfault on arm64
To manage
This seems fine, but I haven't been able to reproduce the failure
anymore, at least not on arm64. I wanted to check in dmesg if there was
also a BUS error.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
This seems fine, but I haven't been able to reproduce the failure
anymore, at least not on arm64. I wanted to check in dmesg if there was
also a BUS error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
During my tests the debdiff attached fixed the DEP-8 tests on arm64 and
the build in armhf. @Andreas could you please test it on your side?
** Attachment added: "debdiff"
https://bugs.launchpad.net/ubuntu/+source/ruby-ferret/+bug/1843804/+attachment/5307724/+files/debdiff
--
You received
This Debian bug might be related: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=918383
** Bug watch added: Debian Bug tracker #918383
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918383
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Lucas subbing you to take a look at, maybe you can help it get progress
upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804
Title:
DEP8 segfault on arm64
To manage notifications about
** Changed in: ruby-ferret (Ubuntu)
Status: New => Triaged
** Changed in: ruby2.5 (Ubuntu)
Status: New => Triaged
** Changed in: ruby-ferret (Ubuntu)
Importance: Undecided => High
** Changed in: ruby2.5 (Ubuntu)
Importance: Undecided => High
** Tags added: server-next
--
By blocking the ruby2.5 migration this also affects ruby2.5 (for
tracking)
** Also affects: ruby2.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ruby2.5 in Ubuntu.
By blocking the ruby2.5 migration this also affects ruby2.5 (for
tracking)
** Also affects: ruby2.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
By blocking the glibc migration this also affects glibc (for tracking)
** Also affects: glibc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: glibc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843804
Title:
DEP8 segfault on arm64
To manage notifications about this bug go to:
The test also passes if I drop this hunk from
d/p/disable_load_path_manipulation.patch:
https://salsa.debian.org/ruby-team/ruby-
ferret/blob/master/debian/patches/disable_load_path_manipulation.patch#L18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Filed upstream, fwiw: https://github.com/jkraemer/ferret/issues/16
** Bug watch added: github.com/jkraemer/ferret/issues #16
https://github.com/jkraemer/ferret/issues/16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To reproduce the segfault without having to run the full test suite, run
this from within the root of the ruby-ferret source package directory:
export RUBYLIB=.
And then:
ruby2.5 debian/ruby-tests.rb
or
gdb ruby2.5
r debian/ruby-tests.rb
--
You received this bug notification because you are
If I change this test to use another directory:
test/unit/index/tc_index.rb:
def test_key_used_for_id_field
fs_path = File.expand_path(File.join(File.dirname(__FILE__),
'../../temp/fsdir'))
...
Like:
fs_path = File.expand_path(File.join(File.dirname(__FILE__),
'../../temp/fsdir2'))
24 matches
Mail list logo
