Bug 2341335

Summary: scx_c_schedulers: FTBFS in Fedora rawhide/f42
Product: [Fedora] Fedora Reporter: Fedora Release Engineering <releng>
Component: scx_c_schedulersAssignee: Jordan Rome <jordan>
Status: NEW --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: davide, jordan, jordan, righi.andrea, tstellar
Target Milestone: ---Flags: jordan: needinfo? (davide)
righi.andrea: needinfo? (jordan)
jordan: needinfo? (righi.andrea)
tstellar: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
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: 2300528, 2339432    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Fedora Release Engineering 2025-01-22 21:55:47 UTC
scx_c_schedulers failed to build from source in Fedora rawhide/f42

https://koji.fedoraproject.org/koji/taskinfo?taskID=128145903


For details on the mass rebuild see:

https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
Please fix scx_c_schedulers at your earliest convenience and set the bug's status to
ASSIGNED when you start fixing it. If the bug remains in NEW state for 8 weeks,
scx_c_schedulers will be orphaned. Before branching of Fedora 43,
scx_c_schedulers will be retired, if it still fails to build.

For more details on the FTBFS policy, please visit:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

Comment 1 Fedora Release Engineering 2025-01-22 21:55:49 UTC
Created attachment 2072525 [details]
build.log

file build.log too big, will only attach last 32768 bytes

Comment 2 Fedora Release Engineering 2025-01-22 21:55:51 UTC
Created attachment 2072526 [details]
root.log

file root.log too big, will only attach last 32768 bytes

Comment 3 Fedora Release Engineering 2025-01-22 21:55:52 UTC
Created attachment 2072527 [details]
state.log

Comment 4 Aoife Moloney 2025-02-26 13:45:17 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 42 development cycle.
Changing version to 42.

Comment 5 Tom Stellard 2025-07-05 21:02:17 UTC
This still fails to build on rawhide, any plans to fix this?

https://koji.fedoraproject.org/koji/taskinfo?taskID=134617121

Comment 6 Tom Stellard 2025-08-12 22:57:59 UTC
@jordan have you had a chance to look at this?

Comment 7 Jordan Rome 2025-09-05 15:03:17 UTC
My apologies. I haven't worked on a scx in many many months. Looping other folks who might be able to help.

@righi.andrea @davide

Comment 8 Andrea Righi 2025-09-09 09:02:59 UTC
Hi @jordan,

we no longer package the C schedulers, as they are intended only for developer use. The Rust schedulers are the only ones we consider
production-ready. Should we go ahead and just drop the scx_c_schedulers package?

Comment 9 Jordan Rome 2025-10-27 10:47:20 UTC
@righi.andrea That works for me. I just gotta find the time to do that :) If you know how or have the ability to, please do.

Comment 10 Fedora Release Engineering 2026-05-06 12:22:48 UTC
This message is a reminder that Fedora Linux 42 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 42 on 2026-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '42'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 42 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.