From the detailed description, I'd say these are not exceptional issues.
They happen from time to time.

https://bugs.ruby-lang.org/issues/16492

I see you have already commented on the ticket, so you could have
remember :)


Vít


Dne 25. 05. 20 v 17:16 Jun Aruga napsal(a):
> I tried to run the Ruby 2.7 module builds with
> https://src.fedoraproject.org/modules/ruby/tree/master ruby.yaml,
> using the rpms/ruby master HEAD on 22th May.
>
> Now when running `fedpkg module-build` command, it is built on 5
> builtroots f33, f32, f31, f30, el8.
> Maybe the el8 target was added recently.
>
> ```
> $ fepkg co modules/ruby
> $ cd ruby
> $ fedpkg module-build
> Submitting the module build...
> The builds 8964, 8965, 8966, 8967 and 8968 were submitted to the MBS
> Build URLs:
> https://mbs.fedoraproject.org/module-build-service/2/module-builds/8964
> https://mbs.fedoraproject.org/module-build-service/2/module-builds/8965
> https://mbs.fedoraproject.org/module-build-service/2/module-builds/8966
> https://mbs.fedoraproject.org/module-build-service/2/module-builds/8967
> https://mbs.fedoraproject.org/module-build-service/2/module-builds/8968
> ```
>
> ## Result
>
> Seeing the current result of the builds, there are 3 kinds of failures.
>
> 1. s390x specific failures. Segmentation Fault in tests. (f33, f32, f31)
>   But when running the scratch build for rpms/ruby today 25th May, it 
> succeeded.
>   https://koji.fedoraproject.org/koji/taskinfo?taskID=44954981
>   Do you know what is the reason for the error?
>
> 2. The failure of `checksec --file=libruby.so.2.7.1` (f30)
>   Possibly checksec 1.11.1-1.fc30, the old version does not support
> --file option.
>   To avoid running checksec on f30, I am planning to set the following
> macro in modules/ruby ruby.yaml.
>
> ```
>      buildopts:
>          rpms:
>              macros: |
>                  %_without_hardening_test 1
> ```
>
> 3. error: one or more PCH files were found, but they were invalid (el8).
>   This is a known issue on the RHEL8 gcc setting.
>   https://bugzilla.redhat.com/show_bug.cgi?id=1721553
>   I think Fedora rawhide rpms/ruby ruby.spec needs to add a %if logic
> to skip the tests on el8 target.
>   Or it needs to add this kind of logic:
>
>     %bcond_without jit_pch
>
>
> Any opinions to fix this?
>
>
> ## Detail log
>
> ### f33 (rawhide)
>
> $ fedpkg module-build-info 8965
>   f33: FAILED: ruby:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=44825779
>
> s390x: https://kojipkgs.fedoraproject.org//work/tasks/5879/44825879/build.log
>   1) Error:
> TestBugReporter#test_bug_reporter_add:
> Timeout::Error: execution of assert_in_out_err expired timeout (30 sec)
> pid 2477783 killed by SIGKILL (signal 9)
>
> ### f32
>
> $ fedpkg module-build-info 8966
>   f32: FAILED: ruby:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=44824056
>
> s390x: https://kojipkgs.fedoraproject.org//work/tasks/4292/44824292/build.log
>   1) Failure:
> Fiddle::TestFunction#test_nogvl_poll
> [/builddir/build/BUILD/ruby-2.7.1/test/fiddle/test_function.rb:95]:
> slept amount of time.
> Expected |200 - 714| (514) to be <= 180.
>   2) Error:
> TestBugReporter#test_bug_reporter_add:
> Timeout::Error: execution of assert_in_out_err expired timeout (30 sec)
> pid 229068 killed by SIGKILL (signal 9)
>
> ### f31
>
> $ fedpkg module-build-info 8967
>   f31: FAILED: ruby:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=44824127
>
> s390x: https://kojipkgs.fedoraproject.org//work/tasks/4208/44824208/build.log
>   1) Error:
> TestIO#test_dup_many:
> Timeout::Error: execution of assert_separately expired timeout (10 sec)
> pid 2679628 exit 1
>   2) Error:
> TestProcess#test_status_quit:
> Timeout::Error: execution of assert_in_out_err expired timeout (10 sec)
> pid 2682640 killed by SIGKILL (signal 9)
> |-
>     /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:1446:in
> `block in test_status_quit'
>     /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:37:in
> `block (2 levels) in with_tmpchdir'
>     /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:36:in `chdir'
>     /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:36:in
> `block in with_tmpchdir'
>     /builddir/build/BUILD/ruby-2.7.1/lib/tmpdir.rb:89:in `mktmpdir'
>     /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:34:in
> `with_tmpchdir'
>     /builddir/build/BUILD/ruby-2.7.1/test/ruby/test_process.rb:1445:in
> `test_status_quit'
>   3) Error:
> TestRubyOptions#test_segv_test:
> Timeout::Error: execution of assert_in_out_err expired timeout (10 sec)
> pid 2683275 killed by SIGABRT (signal 6) (core dumped)
>
> ### f30
>
> $ fedpkg module-build-info 8964
>   f30: FAILED: ruby:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=44825807
>
> Error on all the architectures.
> x86_64, and etc:
> checksec: 1.11.1-1.fc30
>
> https://kojipkgs.fedoraproject.org//work/tasks/5913/44825913/build.log
> + cd ruby-2.7.1
> + checksec --file=libruby.so.2.7.1
> + grep 'Full RELRO.*Canary found.*NX enabled.*DSO.*No RPATH.*No
> RUNPATH.*Yes.*\d*.*\d*.*libruby.so.2.7.1'
>
> ### el8
>
> $ fedpkg module-build-info 8968
>   el8: FAILED: ruby:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=44823939
> https://kojipkgs.fedoraproject.org//work/tasks/4041/44824041/build.log
> Error on all the architectures.
>
>   1) Failure:
> TestJIT#test_attr_reader
> [/builddir/build/BUILD/ruby-2.7.1/test/ruby/test_jit.rb:812]:
> Expected 2 times of JIT success, but succeeded 0 times.
> ...
> /tmp/_ruby_mjit_p2552165u0.c:1:41: error: one or more PCH files were
> found, but they were invalid
>  #include "/tmp/_ruby_mjit_hp2552165u0.h"
>                                          ^
> ...
>
>
> Cheers,
> Jun
>
_______________________________________________
ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org
To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/ruby-sig@lists.fedoraproject.org

Reply via email to