I have reported this here:
https://bugzilla.redhat.com/show_bug.cgi?id=2040380
And I'd appreciate any help to figure out what is going on.
Vít
Dne 12. 01. 22 v 19:33 Vít Ondruch napsal(a):
So as I already mentioned, the following fails:
~~~
$ ./miniruby -I./lib -I. -I.ext/common
So as I already mentioned, the following fails:
~~~
$ ./miniruby -I./lib -I. -I.ext/common ./tool/runruby.rb --extout=.ext
-- --disable-gems "./test/runner.rb" --ruby="./miniruby -I./lib -I.
-I.ext/common ./tool/runruby.rb --extout=.ext -- --disable-gems"
--excludes-dir=./test/excludes
I wish I had answers for you.
Nevertheless, I'd help if I knew how to debug the detached children
after fork, because they are failing earlier then the main process. I
was using `set follow-fork-mode child` but that does nothing :/
I think that exec or fork is the culprit, in some way.
Vít
On 1/11/22 13:45, Vít Ondruch wrote:
> Thread 1 "ruby" received signal SIGABRT, Aborted.
> 0x778a764c in __pthread_kill_implementation () from /lib64/libc.so.6
> Missing separate debuginfos, use: dnf debuginfo-install
> glibc-2.34.9000-36.fc36.x86_64 gmp-6.2.1-1.fc36.x86_64
>
On 1/10/22 14:04, Miro Hrončok wrote:
> On 10. 01. 22 18:14, Miro Hrončok wrote:
>> On 08. 01. 22 18:09, Carlos O'Donell wrote:
>>> On 1/8/22 04:37, Miro Hrončok wrote:
Hello packagers,
I intent to rebuild the following packages with libffi 3.4 in Rawhide...
>>
>> -
>>
>>
I get somewhere:
~~~
$ gdb --args ./miniruby -I./lib -I. -I.ext/common ./tool/runruby.rb
--extout=.ext -- --disable-gems "./test/runner.rb" --ruby="./miniruby
-I./lib -I. -I.ext/common ./tool/runruby.rb --extout=.ext --
--disable-gems" --excludes-dir=./test/excludes
Dne 11. 01. 22 v 17:21 Vít Ondruch napsal(a):
Dne 10. 01. 22 v 18:18 Vít Ondruch napsal(a):
Dne 10. 01. 22 v 18:07 Miro Hrončok napsal(a):
On 10. 01. 22 15:33, Miro Hrončok wrote:
On 10. 01. 22 10:56, Vít Ondruch wrote:
Dne 08. 01. 22 v 18:09 Carlos O'Donell napsal(a):
Dne 10. 01. 22 v 18:18 Vít Ondruch napsal(a):
Dne 10. 01. 22 v 18:07 Miro Hrončok napsal(a):
On 10. 01. 22 15:33, Miro Hrončok wrote:
On 10. 01. 22 10:56, Vít Ondruch wrote:
Dne 08. 01. 22 v 18:09 Carlos O'Donell napsal(a):
On 09. 01. 22 11:07, Miro Hrončok wrote:
On 08. 01. 22 10:37, Miro Hrončok wrote:
Hello packagers,
I intent to rebuild the following packages with libffi 3.4 in Rawhide side
tag f36-build-side-49314 today.
The previous version remains available as libffi13.1, so failures to build
will not
On 10. 01. 22 18:14, Miro Hrončok wrote:
On 08. 01. 22 18:09, Carlos O'Donell wrote:
On 1/8/22 04:37, Miro Hrončok wrote:
Hello packagers,
I intent to rebuild the following packages with libffi 3.4 in Rawhide...
-
Not yet rebuilt packages:
$ repoquery -q --repo=koji --whatrequires
Dne 10. 01. 22 v 18:07 Miro Hrončok napsal(a):
On 10. 01. 22 15:33, Miro Hrončok wrote:
On 10. 01. 22 10:56, Vít Ondruch wrote:
Dne 08. 01. 22 v 18:09 Carlos O'Donell napsal(a):
https://copr.fedorainfracloud.org/coprs/churchyard/libffi-3.4/package/ruby/
Segmentation fault
FAIL 1/1489
On 08. 01. 22 18:09, Carlos O'Donell wrote:
On 1/8/22 04:37, Miro Hrončok wrote:
Hello packagers,
I intent to rebuild the following packages with libffi 3.4 in Rawhide side tag
f36-build-side-49314 today.
Thank you for helping with the rebuilds!
The previous version remains available as
On 10. 01. 22 15:33, Miro Hrončok wrote:
On 10. 01. 22 10:56, Vít Ondruch wrote:
Dne 08. 01. 22 v 18:09 Carlos O'Donell napsal(a):
https://copr.fedorainfracloud.org/coprs/churchyard/libffi-3.4/package/ruby/
Segmentation fault
FAIL 1/1489 tests failed
This failed in the same place in two
On 10. 01. 22 10:56, Vít Ondruch wrote:
Dne 08. 01. 22 v 18:09 Carlos O'Donell napsal(a):
https://copr.fedorainfracloud.org/coprs/churchyard/libffi-3.4/package/ruby/
Segmentation fault
FAIL 1/1489 tests failed
This failed in the same place in two different builds in the test_ractor.rb
(Ruby
Hello packagers,
I intent to rebuild the following packages with libffi 3.4 in Rawhide side tag
f36-build-side-49314 today.
The previous version remains available as libffi13.1, so failures to build will
not result in uninstallable packages.
You can inspect some known failures:
Dne 08. 01. 22 v 18:09 Carlos O'Donell napsal(a):
https://copr.fedorainfracloud.org/coprs/churchyard/libffi-3.4/package/ruby/
Segmentation fault
FAIL 1/1489 tests failed
This failed in the same place in two different builds in the test_ractor.rb
(Ruby Ractor)
test case, and it crashes in
On 08. 01. 22 10:37, Miro Hrončok wrote:
Hello packagers,
I intent to rebuild the following packages with libffi 3.4 in Rawhide side tag
f36-build-side-49314 today.
The previous version remains available as libffi13.1, so failures to build will
not result in uninstallable packages.
You
On 08. 01. 22 10:37, Miro Hrončok wrote:
I intent to rebuild the following packages with libffi 3.4 in Rawhide side tag
f36-build-side-49314 today.
The update: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c440651258
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
On 08. 01. 22 18:09, Carlos O'Donell wrote:
https://copr.fedorainfracloud.org/coprs/churchyard/libffi-3.4/package/cjs/
https://copr.fedorainfracloud.org/coprs/churchyard/libffi-3.4/package/gjs/
both "killed by signal 11 SIGSEGV"
Right, this is because there is an ordering dependency between
On 1/8/22 04:37, Miro Hrončok wrote:
> Hello packagers,
>
> I intent to rebuild the following packages with libffi 3.4 in Rawhide side
> tag f36-build-side-49314 today.
Thank you for helping with the rebuilds!
> The previous version remains available as libffi13.1, so failures to build
>
On 08. 01. 22 10:37, Miro Hrončok wrote:
Hello packagers,
I intent to rebuild the following packages with libffi 3.4 in Rawhide side tag
f36-build-side-49314 today.
The previous version remains available as libffi13.1, so failures to build will
not result in uninstallable packages.
You
Hello packagers,
I intent to rebuild the following packages with libffi 3.4 in Rawhide side tag
f36-build-side-49314 today.
The previous version remains available as libffi13.1, so failures to build will
not result in uninstallable packages.
You can inspect some known failures:
22 matches
Mail list logo
