Bug 2127458

Summary: bear: FTBFS in Fedora Rawhide
Product: [Fedora] Fedora Reporter: Ben Beasley <code>
Component: bearAssignee: Ben Beasley <code>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: code, dan.cermak, epel-packagers-sig, thofmann, vitaly
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://koschei.fedoraproject.org/package/bear
Whiteboard:
Fixed In Version: bear-3.0.20-5.fc38 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-15 16:38:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2140814    
Attachments:
Description Flags
Scratch-build log none

Description Ben Beasley 2022-09-16 12:39:01 UTC 
Description of problem:
Package bear fails to build from source in Fedora Rawhide.

Version-Release number of selected component (if applicable):
3.0.20-2.fc38

Steps to Reproduce:
koji build --scratch f38 bear-3.0.20-2.fc38.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/bear

-----

Koschei hasn’t yet had a failing rebuild yet, but this is reproducible with any scratch build, e.g.: https://koji.fedoraproject.org/koji/taskinfo?taskID=92075476

The stack traces point into grpc routines, so it’s possible that this is actually a grpc bug. It seems like it might be related to the update from grpc 1.48.0 to 1.48.1; I did not do impact/regression testing for that since it was only a patch release. The failures are only on s390x. (I have always had to skip a lot of undiagnosed test failures for grpc on s390x.)

It may be that it is worth setting this bug to block F-ExcludeArch-s390x and adding ExcludeArch: s390x to the bear spec file. Since bear is a leaf package, this would not have much impact. Or, maybe you prefer to skip the affected test(s).

What do you think?
Comment 1 Ben Beasley 2022-09-16 12:39:44 UTC 
Created attachment 1912320 [details]
Scratch-build log
Comment 2 Ben Beasley 2022-11-04 01:53:39 UTC 
*** Bug 2139903 has been marked as a duplicate of this bug. ***
Comment 3 Ben Beasley 2022-11-04 01:55:52 UTC 
This bug was reported again when the package was rebuilt (unsuccessfully) for an spdlog version bump. What do you think we should do?

It’s possible that the problem will go away again with a fully updated grpc/protobuf/whatnot, but I haven’t been able to get that lined up yet.
Comment 4 Vitaly 2022-11-04 08:14:43 UTC 
> It may be that it is worth setting this bug to block F-ExcludeArch-s390x and adding ExcludeArch: s390x to the bear spec file.

I have a better option - skip failed test on s390x.
Comment 5 Ben Beasley 2022-11-04 08:45:45 UTC 
(In reply to Vitaly Zaitsev from comment #4)
> > It may be that it is worth setting this bug to block F-ExcludeArch-s390x and adding ExcludeArch: s390x to the bear spec file.
> 
> I have a better option - skip failed test on s390x.

(In reply to Ben Beasley from comment #0)
> It may be […]. Or, maybe you prefer to skip the
> affected test(s).

Indeed, that’s a reasonable option.
Comment 6 Ben Beasley 2022-11-15 14:14:33 UTC 
Since I haven’t heard anything from Dan, I’m going to proceed with skipping the test. I don’t mind at all if this is reverted later in favor of some other solution.
Comment 7 Fedora Update System 2022-11-15 16:10:17 UTC 
FEDORA-2022-d5b05d4688 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d5b05d4688
Comment 8 Fedora Update System 2022-11-15 16:38:50 UTC 
FEDORA-2022-d5b05d4688 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.