Description of problem: If I uncomment the chroot_scan plugin options in site-defaults.cfg so as to gather logs and core files, it seems to sit for a long time in this state: 16724 pts/0 S+ 0:00 | \_ /usr/bin/python /usr/bin/fedpkg mockbuild 16748 pts/0 S+ 0:04 | \_ /usr/bin/python -tt /usr/sbin/mock -r fedora-20-x86_64 --resultdir /data/fedora/cross-binutils/results_cross-binutils/2.25/3.fc20 --rebuild /data/fedora/cross-binutils/cross-binutils-2.25-3.fc20.src.rpm 9142 pts/0 R+ 0:10 | \_ cp --parents /var/lib/mock/fedora-20-x86_64/root/proc/kcore /data/fedora/cross-binutils/results_cross-binutils/2.25/3.fc20/chroot_scan It appears that the config, as below: config_opts['plugin_conf']['chroot_scan_enable'] = True config_opts['plugin_conf']['chroot_scan_opts'] = { # Regexp of files which should be copied from buildroot to resultdir. 'regexes': [ "core(\.\d+)?", "\.log$",], # If set to True files are copied only if build failed. 'only_failed': False, } doesn't exclude procfs files such as /proc/kcore. Version-Release number of selected component (if applicable): mock-1.2.8-1.fc21.noarch How reproducible: 100% Steps to Reproduce: 1. Uncomment config lines 2. fedpkg mockbuild something. I'm using cross-binutils with the specfile modified to have build_all set to 0 and build_x86_64 set to 1. Actual results: Sits for a long time copying /proc/kcore (I assume it finishes at some point, but will sit for at least 15 minutes). Expected results: Shouldn't pick up /proc/kcore, but should pick up various config.log files generated by the build. Additional info: See also: https://bugzilla.redhat.com/show_bug.cgi?id=1190763
I changed the regexp to: "^[^k]?core(\.\d+)?" It is not ideal and robust, but should work in this case. I have robust regexp, but it is hard to read and understand and I do not think such string should be in examples. Ideas for regexp which does not match kcore but match usual coredumps names are welcome. Fixed in commit: * be95515 do not include kcore in default regexp for chroot_scan plugin [RHBZ#1219432]
This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23
mock-1.2.13-2.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16053
mock-1.2.13-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16054
mock-1.2.13-2.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16056
mock-1.2.13-2.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-8114
mock-1.2.13-2.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-8115
mock-1.2.13-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update mock'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16054
mock-1.2.13-2.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update mock'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16056
mock-1.2.13-2.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update mock'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16053
mock-1.2.13-2.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update mock'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-8115
mock-1.2.13-2.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update mock'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-8114
mock-1.2.13-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.13-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.13-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.13-2.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.
mock-1.2.13-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.