Learn more about these different git repos.
Other Git URLs
Describe the issue The latest Macaulay2 build seems to be stuck in a build loop on s390x: https://koji.fedoraproject.org/koji/buildinfo?buildID=2042481. Can anything be done to let the build finish? (I was hoping to do this build for Fedora 36, too...)
When do you need this? (YYYY/MM/DD) Soon.
When is this no longer needed or useful? (YYYY/MM/DD) Never.
If we cannot complete your request, what is the impact? We can't update Macaulay2 to its latest version, or we have to exclude the s390x architecture.
The restarts were likely systemd-oomd re-running even tho I thought I had disabled.
Now it's just not finishing...
|-kojid,665942 /usr/sbin/kojid --fg --force-lock --verbose | `-kojid,665943 /usr/sbin/kojid --fg --force-lock --verbose | `-mock,666355 -tt /usr/libexec/mock/mock -r koji/f37-build-37279034-4751534 --old-chroot --no-clean --target s390x ... | `-rpmbuild,668940 -bb --target s390x --nodeps /builddir/build/SPECS/Macaulay2.spec | `-sh,669251 -e /var/tmp/rpm-tmp.jNgA1J | `-make,673938 -C BUILD/s390x-redhat-linux-gnu VERBOSE=true Verbose=true IgnoreExampleErrors=true | `-make,724579 -C Macaulay2 all | `-make,728312 -C packages all | `-M2-binary,729243 -q --stop--silen | |-{M2-binary},729246 | |-{M2-binary},729247 | |-{M2-binary},729248 | |-{M2-binary},729249 | |-{M2-binary},729250 | |-{M2-binary},729251 | |-{M2-binary},729298 | |-{M2-binary},729299 | `-cat,729711
kojibui+ 729243 70.9 1.3 1832132 230416 ? Sl Aug06 1110:21 /builddir/build/BUILD/M2-release-1.20/M2/BUILD/s390x-redhat-linux-gnu/usr-dist/s390x-Linux-Fedora-37/bin/M2-binary -q --stop --silent --no-preload -e errorDepth=0 -e debugLevel=0 -e installPackage("Macaulay2Doc", MakeDocumentation => true, MakeHTML => true, MakeInfo => true, MakePDF => false, RemakeAllDocumentation => false, IgnoreExampleErrors => true, RerunExamples => false, CheckDocumentation => true, UserMode => false, Verbose => true, InstallPrefix => "/builddir/build/BUILD/M2-release-1.20/M2/BUILD/s390x-redhat-linux-gnu/usr-dist/", SeparateExec => true, DebuggingMode => true); exit 0
An strace:
[pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729251] <... clock_nanosleep resumed>0x3ff3df767b0) = 0 [pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729251] <... clock_nanosleep resumed>0x3ff3df767b0) = 0 [pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729251] <... clock_nanosleep resumed>0x3ff3df767b0) = 0 [pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729251] <... clock_nanosleep resumed>0x3ff3df767b0) = 0 [pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729251] <... clock_nanosleep resumed>0x3ff3df767b0) = 0 [pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729251] <... clock_nanosleep resumed>0x3ff3df767b0) = 0 [pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729251] <... clock_nanosleep resumed>0x3ff3df767b0) = 0 [pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729251] <... clock_nanosleep resumed>0x3ff3df767b0) = 0 [pid 729250] <... clock_nanosleep resumed>0x3ff3e7777b0) = 0 [pid 729251] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0}, <unfinished ...> [pid 729250] clock_nanosleep(CLOCK_REALTIME, 0, {tv_sec=1, tv_nsec=0},
The cat there is odd... not sure what else is going on or I can check. ;(
Metadata Update from @phsmoura: - Issue tagged with: low-gain, low-trouble, ops
Builds are running, closing.
Metadata Update from @humaton: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.