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?
Created attachment 1912320 [details] Scratch-build log
*** Bug 2139903 has been marked as a duplicate of this bug. ***
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.
> 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 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.
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.
FEDORA-2022-d5b05d4688 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d5b05d4688
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.