Dne 17. 01. 23 v 15:38 Mamoru TASAKA napsal(a):
Vít Ondruch wrote on 2023/01/17 23:31:This seems to be never ending story 🤦🏻♂️https://koschei.fedoraproject.org/package/rubygem-mail?collection=f38 VítWell, I've noticed this, so I tried to reproduce, but it seems unreproducible.I suspected: * This is due to rspec-expectations 3.12.1 -> 3.12.2 * Or aarch64 specific: But neither of the above seems to be the reason: At least koji build is successful and mockbuild on my local disc is also successful. https://koji.fedoraproject.org/koji/taskinfo?taskID=96250590
Interesting 🤔 One thing I have noticed is this in build done by Koschei: ~~~ -Building target platforms: noarch -Building for target noarch ~~~ vs your Koji build: ~~~ +Building target platforms: aarch64 +Building for target aarch64 ~~~The other possibility is the order of test cases and seed. However not sure if the spec order might be random actually.
Vít
MamoruDne 07. 02. 22 v 12:24 Vít Ondruch napsal(a):Dear Mamoru,Could you please check the following two packages which recently started to fail?https://koschei.fedoraproject.org/package/rubygem-webmock?collection=f36https://koschei.fedoraproject.org/package/rubygem-websocket-extensions?collection=f36I suspect that this is related to the RSpec update, but the errors are quite strange on the first look:~~~1) WebMock::RequestSignature initialization assigns normalized headers Failure/Error: @headers = WebMock::Util::Headers.normalize_headers(headers) #<WebMock::Util::Headers (class)> received :normalize_headers with unexpected argumentsexpected: ({"A"=>"a"}) got: ({"A"=>"a"}) # ./lib/webmock/request_signature.rb:25:in `headers=' # ./lib/webmock/request_signature.rb:49:in `assign_options' # ./lib/webmock/request_signature.rb:11:in `initialize' # ./spec/unit/request_signature_spec.rb:23:in `new'# ./spec/unit/request_signature_spec.rb:23:in `block (3 levels) in <top (required)>' # ./lib/webmock/rspec.rb:37:in `block (2 levels) in <top (required)>'~~~ Thx a lot VítP.S. Sorry for not being more helpful, I have to spent some time with CentOS Stream 9 to get Ruby into shape there, especially the problematic SystemTap support [1].[1] https://bugs.ruby-lang.org/issues/18257_______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList 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_______________________________________________ ruby-sig mailing list -- ruby-sig@lists.fedoraproject.org To unsubscribe send an email to ruby-sig-le...@lists.fedoraproject.orgFedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelinesList 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
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ 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
