Description of problem: Break mock build Version-Release number of selected component: mock-3.5-2.fc38 Additional info: reporter: libreport-2.17.9 kernel: 6.3.0-0.rc6.20230412gite62252bc55b6.51.fc39.x86_64+debug cmdline: /usr/bin/python3 -tt /usr/libexec/mock/mock -r fedora-rawhide-x86_64 --resultdir /home/mikhail/packaging-work/mutter/results_mutter/44.0/4.fc39 --rebuild /home/mikhail/packaging-work/mutter/mutter-44.0-4.fc39.src.rpm cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-5595c7bd-4438-49b6-9bcd-144c74086b63.scope uid: 0 reason: file_util.py:68:rmtree:OSError: [Errno 39] Directory not empty: '/var/lib/mock/fedora-rawhide-x86_64/root/builddir/build/BUILD/mesa-f8a8b7708e33ff22dd71c68830c33abe3fb1030a/redhat-linux-build/src/gallium/winsys/sw' executable: /usr/libexec/mock/mock type: Python3 package: mock-3.5-2.fc38 runlevel: N 5 exception_type: KeyboardInterrupt crash_function: rmtree interpreter: python3-3.11.3-1.fc39.x86_64 comment: Break mock build Truncated backtrace: #1 [/usr/lib/python3.11/site-packages/mockbuild/file_util.py:68] rmtree #2 [/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py:93] trace #3 [/usr/lib/python3.11/site-packages/mockbuild/file_util.py:59] rmtree #4 [/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py:93] trace #5 [/usr/lib/python3.11/site-packages/mockbuild/file_util.py:59] rmtree #6 [/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py:93] trace #7 [/usr/lib/python3.11/site-packages/mockbuild/file_util.py:59] rmtree #8 [/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py:93] trace #9 [/usr/lib/python3.11/site-packages/mockbuild/file_util.py:59] rmtree #10 [/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py:93] trace #11 [/usr/lib/python3.11/site-packages/mockbuild/file_util.py:59] rmtree #12 [/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py:93] trace #13 [/usr/lib/python3.11/site-packages/mockbuild/buildroot.py:884] delete #14 [/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py:93] trace #15 [/usr/lib/python3.11/site-packages/mockbuild/backend.py:97] clean #16 [/usr/lib/python3.11/site-packages/mockbuild/trace_decorator.py:93] trace #17 [/usr/lib/python3.11/site-packages/mockbuild/rebuild.py:23] rebuild_generic
Created attachment 1957379 [details] File: os_info
Created attachment 1957380 [details] File: environ
Created attachment 1957381 [details] File: mountinfo
Created attachment 1957382 [details] File: open_fds
Created attachment 1957383 [details] File: namespaces
Created attachment 1957384 [details] File: backtrace
Created attachment 1957385 [details] File: cpuinfo
Proposed fix: https://github.com/rpm-software-management/mock/pull/1058
*** Bug 2176689 has been marked as a duplicate of this bug. ***
*** Bug 2177680 has been marked as a duplicate of this bug. ***
*** Bug 2218922 has been marked as a duplicate of this bug. ***
*** Bug 2169055 has been marked as a duplicate of this bug. ***
*** Bug 2181641 has been marked as a duplicate of this bug. ***
*** Bug 2213874 has been marked as a duplicate of this bug. ***
(In reply to Miroslav Suchý from comment #8) > Proposed fix: > https://github.com/rpm-software-management/mock/pull/1058 The patch is merged now. And I believe the following patch is actually going to resolve all such problems in the future itself: https://github.com/rpm-software-management/mock/pull/1133/files Simply put, if any exception (including KeyboardInterrupt) was raised at the same time Mock was installing something using a package manager, we did not properly kill the orphaned in-chroot process, which blocked the subsequent cleanup && umount. This should be fixed in Mock 5.0+. The exception (signal) handler is not immune against subsequent KeyboardInterrupts - so users shouldn't press CTRL+C twice in a row.
*** Bug 2176691 has been marked as a duplicate of this bug. ***