Closed
Bug 1912223
Opened 4 months ago
Closed 4 months ago
Perma Android 5.0 ARMv7 opt bootstrap [tier 2] Failed to emerge dev-vcs/mercurial-6.6.2, Log file: E | followed by ERROR: dev-vcs/mercurial-6.6.2::gentoo failed (compile phase):
Categories
(Firefox Build System :: Bootstrap Configuration, defect)
Firefox Build System
Bootstrap Configuration
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: imoraru, Unassigned)
References
Details
Failure summary is empty in treeherder.
>>> Completed installing dev-python/uc-micro-py-1.0.3 into /var/tmp/portage/dev-python/uc-micro-py-1.0.3/image
[32m*[0m Final size of build directory: 276 KiB
[32m*[0m Final size of installed tree: 324 KiB
[32m*[0m Verifying compiled files for python3.12
>>> Installing ([33;01m14[39;49;00m of [33;01m21[39;49;00m) [32mdev-python/uc-micro-py-1.0.3::gentoo[39;49;00mE]0;7693ad32dd63: emerge: (14 of 21) dev-python/uc-micro-py-1.0.3 MergeUnable to unshare: EPERM (for FEATURES="ipc-sandbox network-sandbox pid-sandbox")
Unable to unshare: EPERM (for FEATURES="ipc-sandbox network-sandbox pid-sandbox")
]0;7693ad32dd63: emerge: (14 of 21) dev-python/uc-micro-py-1.0.3 Clean Post
>>> Completed ([33;01m14[39;49;00m of [33;01m21[39;49;00m) [32mdev-python/uc-micro-py-1.0.3::gentoo[39;49;00mE
>>> Emerging ([33;01m15[39;49;00m of [33;01m21[39;49;00m) [32mdev-vcs/mercurial-6.6.2::gentoo[39;49;00mE]0;7693ad32dd63: emerge: (15 of 21) dev-vcs/mercurial-6.6.2 CleanUnable to unshare: EPERM (for FEATURES="ipc-sandbox network-sandbox pid-sandbox")
[32m * [39;49;00mmercurial-6.6.2.tar.gz BLAKE2B SHA512 size ;-) ... [34;01m[ [39;49;00m[32;01mok[39;49;00m[34;01m ][39;49;00m
]0;7693ad32dd63: emerge: (15 of 21) dev-vcs/mercurial-6.6.2 CompileUnable to unshare: EPERM (for FEATURES="pid-sandbox")
Unable to unshare: EPERM (for FEATURES="ipc-sandbox network-sandbox pid-sandbox")
>>> Unpacking source...
>>> Unpacking mercurial-6.6.2.tar.gz to /var/tmp/portage/dev-vcs/mercurial-6.6.2/work
>>> Source unpacked in /var/tmp/portage/dev-vcs/mercurial-6.6.2/work
Unable to unshare: EPERM (for FEATURES="ipc-sandbox network-sandbox pid-sandbox")
>>> Preparing source in /var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2 ...
[32m*[0m Build system packages:
[32m*[0m dev-python/gpep517 : 16
[32m*[0m dev-python/installer : 0.7.0
[32m*[0m dev-python/cython : 3.0.10
[32m*[0m dev-python/setuptools : 71.0.4
[32m*[0m dev-python/setuptools-rust :
[32m*[0m dev-python/setuptools-scm : 8.1.0
[32m*[0m dev-python/wheel : 0.43.0
>>> Source prepared.
Unable to unshare: EPERM (for FEATURES="ipc-sandbox network-sandbox pid-sandbox")
>>> Configuring source in /var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2 ...
>>> Source configured.
Unable to unshare: EPERM (for FEATURES="ipc-sandbox network-sandbox pid-sandbox")
>>> Compiling source in /var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2 ...
[32m*[0m python3_12: running distutils-r1_run_phase python_compile
[32m*[0m Building the wheel for mercurial-6.6.2 via setuptools.build_meta:__legacy__
cargo_env python3.12 -m gpep517 build-wheel --prefix=/usr --backend setuptools.build_meta:__legacy__ --output-fd 3 --wheel-dir /var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2-python3_12/wheel
[31;01m*[0m ERROR: dev-vcs/mercurial-6.6.2::gentoo failed (compile phase):
[31;01m*[0m FATAL: please call cargo_gen_config before using cargo_env
[31;01m*[0m
[31;01m*[0m Call stack:
[31;01m*[0m ebuild.sh, line 136: Called src_compile
[31;01m*[0m environment, line 4776: Called distutils-r1_src_compile
[31;01m*[0m environment, line 2226: Called _distutils-r1_run_foreach_impl 'python_compile'
[31;01m*[0m environment, line 856: Called python_foreach_impl 'distutils-r1_run_phase' 'python_compile'
[31;01m*[0m environment, line 4207: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
[31;01m*[0m environment, line 3717: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
[31;01m*[0m environment, line 3715: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_compile'
[31;01m*[0m environment, line 1291: Called distutils-r1_run_phase 'python_compile'
[31;01m*[0m environment, line 2210: Called python_compile
[31;01m*[0m environment, line 3989: Called distutils-r1_python_compile 'build_ext'
[31;01m*[0m environment, line 2032: Called distutils_pep517_install '/var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2-python3_12/install'
[31;01m*[0m environment, line 2555: Called cargo_env 'python3.12' '-m' 'gpep517' 'build-wheel' '--prefix=/usr' '--backend' 'setuptools.build_meta:__legacy__' '--output-fd' '3' '--wheel-dir' '/var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2-python3_12/wheel'
[31;01m*[0m environment, line 1776: Called die
[31;01m*[0m The specific snippet of code:
[31;01m*[0m [[ -n ${_CARGO_GEN_CONFIG_HAS_RUN} ]] || die "FATAL: please call cargo_gen_config before using ${FUNCNAME}";
[31;01m*[0m
[31;01m*[0m If you need support, post the output of `emerge --info '=dev-vcs/mercurial-6.6.2::gentoo'`,
[31;01m*[0m the complete build log and the output of `emerge -pqv '=dev-vcs/mercurial-6.6.2::gentoo'`.
[31;01m*[0m The complete build log is located at '/var/tmp/portage/dev-vcs/mercurial-6.6.2/temp/build.log'.
[31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/dev-vcs/mercurial-6.6.2/temp/environment'.
[31;01m*[0m Working directory: '/var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2'
[31;01m*[0m S: '/var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2'
>>> [31;01mFailed[39;49;00m to emerge [32mdev-vcs/mercurial-6.6.2[39;49;00m, Log file:E
>>> '[32m/var/tmp/portage/dev-vcs/mercurial-6.6.2/temp/build.log[39;49;00m'E
[32m * [39;49;00mMessages for package [32mdev-vcs/mercurial-6.6.2[39;49;00m:
[31;01m * [39;49;00mERROR: dev-vcs/mercurial-6.6.2::gentoo failed (compile phase):
[31;01m * [39;49;00m FATAL: please call cargo_gen_config before using cargo_env
[31;01m * [39;49;00m
[31;01m * [39;49;00mCall stack:
[31;01m * [39;49;00m ebuild.sh, line 136: Called src_compile
[31;01m * [39;49;00m environment, line 4776: Called distutils-r1_src_compile
[31;01m * [39;49;00m environment, line 2226: Called _distutils-r1_run_foreach_impl 'python_compile'
[31;01m * [39;49;00m environment, line 856: Called python_foreach_impl 'distutils-r1_run_phase' 'python_compile'
[31;01m * [39;49;00m environment, line 4207: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
[31;01m * [39;49;00m environment, line 3717: Called _multibuild_run '_python_multibuild_wrapper' 'distutils-r1_run_phase' 'python_compile'
[31;01m * [39;49;00m environment, line 3715: Called _python_multibuild_wrapper 'distutils-r1_run_phase' 'python_compile'
[31;01m * [39;49;00m environment, line 1291: Called distutils-r1_run_phase 'python_compile'
[31;01m * [39;49;00m environment, line 2210: Called python_compile
[31;01m * [39;49;00m environment, line 3989: Called distutils-r1_python_compile 'build_ext'
[31;01m * [39;49;00m environment, line 2032: Called distutils_pep517_install '/var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2-python3_12/install'
[31;01m * [39;49;00m environment, line 2555: Called cargo_env 'python3.12' '-m' 'gpep517' 'build-wheel' '--prefix=/usr' '--backend' 'setuptools.build_meta:__legacy__' '--output-fd' '3' '--wheel-dir' '/var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2-python3_12/wheel'
[31;01m * [39;49;00m environment, line 1776: Called die
[31;01m * [39;49;00mThe specific snippet of code:
[31;01m * [39;49;00m [[ -n ${_CARGO_GEN_CONFIG_HAS_RUN} ]] || die "FATAL: please call cargo_gen_config before using ${FUNCNAME}";
[31;01m * [39;49;00m
[31;01m * [39;49;00mIf you need support, post the output of `emerge --info '=dev-vcs/mercurial-6.6.2::gentoo'`,
[31;01m * [39;49;00mthe complete build log and the output of `emerge -pqv '=dev-vcs/mercurial-6.6.2::gentoo'`.
[31;01m * [39;49;00mThe complete build log is located at '/var/tmp/portage/dev-vcs/mercurial-6.6.2/temp/build.log'.
[31;01m * [39;49;00mThe ebuild environment file is located at '/var/tmp/portage/dev-vcs/mercurial-6.6.2/temp/environment'.
[31;01m * [39;49;00mWorking directory: '/var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2'
[31;01m * [39;49;00mS: '/var/tmp/portage/dev-vcs/mercurial-6.6.2/work/mercurial-6.6.2'
[32m * [39;49;00mGNU info directory index is up-to-date.
[33;01m * IMPORTANT:[39;49;00m 15 news items need reading for repository 'gentoo'.
[33;01m *[39;49;00m Use [32;01meselect news read[39;49;00m to view new items.
]0;@7693ad32dd63:/[taskcluster 2024-08-08 08:33:45.606Z] === Task Finished ===
[taskcluster 2024-08-08 08:33:45.607Z] Unsuccessful task run with exit code: 1 completed in 179.609 seconds
Reporter | ||
Comment 1•4 months ago
|
||
Hi Johan! Can you please take a look at this?
Thank you!
Flags: needinfo?(jlorenzo)
Reporter | ||
Updated•4 months ago
|
Summary: Perma Android 5.0 ARMv7 opt bootstrap [tier 2] Failed to emerge dev-vcs/mercurial-6.6.2, Log file: E | followed by ERROR: dev-vcs/mercurial-6.6.2::<something> failed (compile phase): → Perma Android 5.0 ARMv7 opt bootstrap [tier 2] Failed to emerge dev-vcs/mercurial-6.6.2, Log file: E | followed by ERROR: dev-vcs/mercurial-6.6.2::gentoo failed (compile phase):
Comment 2•4 months ago
|
||
I'm sorry, I don't know what's happening here. RelEng doesn't own the bootstrap tasks. Transferring to :glandium, in case it's in his wheelhouse.
Flags: needinfo?(jlorenzo) → needinfo?(mh+mozilla)
Comment 3•4 months ago
|
||
It fixed itself. It was a problem upstream in gentoo with mercurial.
Status: NEW → RESOLVED
Closed: 4 months ago
Flags: needinfo?(mh+mozilla)
Resolution: --- → WORKSFORME
Comment 4•4 months ago
|
||
Thanks :glandium!
Comment hidden (Intermittent Failures Robot) |
You need to log in
before you can comment on or make changes to this bug.
Description
•