Learn more about these different git repos.
Other Git URLs
Trying to build Chromium for the fno-omit-frame-pointer proposal in copr fails after > 22h (see https://copr.fedorainfracloud.org/coprs/daandemeyer/fno-omit-frame-pointer/build/4621610/).
It'd be great to have beefier machines available for these kind of larger builds.
We could configure a new pool of AWS VMs (with at least 1 machine preallocated) with more resources. If we wanted to "start beefy VM on demand", RFE needs to be implemented.
We also need to allow users to specify custom build tags, with e.g. tag "expensive_build" which would likely mean (a) longer waiting in the queue (starting phase), but eventually (b) faster overall build.
But I'm not sure what would be the desired performance to finish the chromium build in a reasonable time. And what is the reasonable time.
Metadata Update from @praiskup: - Issue tagged with: RFE
<Eighth_Doctor> being stuck at -j8 or -j10 will take forever <praiskup> so do you claim 8-core machines will not help? <Eighth_Doctor> it will not help <Eighth_Doctor> you probably want at least 48 cores or more <praiskup> what exactly will be achieved with that power? <praiskup> build finished within 24 hoours, or faster? <Eighth_Doctor> yeah <Eighth_Doctor> more cores makes it go way, way, way faster <Eighth_Doctor> the only reason it's limited is because Koji's builders lock up with high parallelism <Eighth_Doctor> but I know Tom removes the limit when building locally <Eighth_Doctor> (on AWS) <praiskup> https://pagure.io/copr/copr/issue/2241 <Eighth_Doctor> OBS uses a constraints declaration system to identify good builders for packages <Eighth_Doctor> https://build.opensuse.org/package/view_file/openSUSE:Factory/chromium/_constraints?expand=1 <Eighth_Doctor> with their constraints, it took 2377 seconds to build for x86_64 <Eighth_Doctor> roughly 40 minutes <praiskup> How many cores were used? <Eighth_Doctor> -j11 <Eighth_Doctor> but it also looks like their build config is different from ours <Eighth_Doctor> a few more system libraries than what we do
hi , I just got the same problem but just on rawhide
please try build it on F36 before, i.e. seems to me that is a specific problem on rawhide
Per IRC chat with @sergiomb, build is stuck on:
<sergiomb> now I see it stuck on python3 ../../tools/grit/grit.py -i ../../chrome/app/resources/locale_settings_linux.grd build -o gen/chrome --depdir . --depfile gen/chrome/app/resources/platform_locale_settings_grit.d --write-only-new=1 --depend-on-stamp -E root_gen_dir=gen -E root_src_dir=../../ -D SHARED_INTERMEDIATE_DIR=gen -D DEVTOOLS_GRD_PATH=gen/third_party/devtools-frontend/src/front_end/devtools_resources -D scale_factors=2x -D _chromium -E CHROMIUM_BUILD=chromium -D desktop_linux -D toolkit_views -D use_aura -D use_nss_certs -D use_ozone -D enable_arcore=false -D enable_background_mode=true -D enable_background_contents=true -D enable_extensions=true -D enable_hangout_services_extension=false -D enable_plugins=true -D enable_print_preview=true -D enable_printing=true -D enable_service_discovery=true -D enable_side_search=false -D enable_supervised_users=false -D enable_vr=false -D enable_webui_tab_strip=true -D safe_browsing_mode=1 -D optimize_webui=false -D enable_feed_v2=false -f gen/tools/gritsettings/default_resource_ids --assert-file-list obj/chrome/app/resources/platform_locale_settings_expected_outputs.txt
See also this Fedora Infra Koji issue.
This issue has been migrated to GitHub: https://github.com/fedora-copr/copr/issues/2241
Metadata Update from @nikromen: - Issue close_status updated to: MIGRATED - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.