On Sat, Oct 1, 2022 at 10:11 AM Vít Ondruch <vondr...@redhat.com> wrote:
> > Dne 29. 09. 22 v 16:23 Mamoru TASAKA napsal(a): > > Vít Ondruch wrote on 2022/09/29 20:15: > >> > > > >> And another issue for Mamoru, this time from rspec-core: > >> > >> > >> ~~~ > >> > >> expected "\nAn error occurred while loading > >> ./spec/example_spec.rb.\nFailure/Error:\n RSpec.describe Fixnum > >> d...files took 0.05699 seconds to load)\n0 examples, 0 failures, 1 > >> error occurred outside of examples\n" not to string includes: "0 > >> examples" > >> Diff: > >> @@ -1,2 +1,22 @@ > >> -0 examples > >> + > >> +An error occurred while loading ./spec/example_spec.rb. > >> +Failure/Error: > >> + RSpec.describe Fixnum do > >> + describe 'inner' do > >> + describe String do > >> + it "is available as described_class" do > >> + expect(described_class).to eq(String) > >> + end > >> + end > >> + end > >> + end > >> + > >> +NameError: > >> + uninitialized constant Fixnum > >> +# ./spec/example_spec.rb:1:in `<top (required)>' > >> +No examples found. > >> + > >> + > >> +Finished in 0.00003 seconds (files took 0.05699 seconds to load) > >> +0 examples, 0 failures, 1 error occurred outside of examples > >> > >> ~~~ > >> > >> > >> And here is the fix: > >> > https://github.com/rspec/rspec-core/commit/bf49c78d7a92e253d557924a3f85fd6991e32ca3 > >> > >> > >> > >> This is likely due to: > >> > https://github.com/ruby/ruby/blob/28840d74c26189f4e730b906c2383e32ea6165fe/NEWS.md?plain=1#L232 > >> > >> > >> > >> In short, it seems to be due to removing deprecated `Fixnum` and > >> `Bignum`. This might cause some troubles. Not in rspec-core. > >> > > > > Okay, backported (with minimum changes): > > > https://src.fedoraproject.org/rpms/rubygem-rspec-core/c/e7531e5398dc0d81fbcdcb9c7b26fb83e009a2e0 > > > > > Thx a lot. > > And I should really update Pry, because I saw Pry related issues on more > places. > > > > > > I guess removal of Fixnum / Bignum / tainted? and so on will affect > > many packages. > > > Yes, that is my worry as well. Probably good idea to keep and eye on the > Copr and report these upstream in advance. > > > BTW, Pavel, would there be a chance to collect the build logs of all the > packages in one tarball? It would probably help to identify some > patterns (that could be possibly also interesting RFE for Copr, rihgt? ;) > ). > I already automatically collect all copr build logs via my automation, locally, using: https://github.com/pvalena/theprototype/blob/main/pkgs/cr-build.sh (documentation + demo TBD) I do intend to go through the failed builds and identify / sort the causes (dependencies vs test suite etc.). But in case you want to grep through them yourself - here're the failed builds & logs for those: https://gist.github.com/pvalena/019f480cb6107d56bbb052e9fc9ceddd https://pvalena.fedorapeople.org/logs/rubygems-testing-logs-ruby-3.2.txz Pavel > > > Vít > >
_______________________________________________ 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
