okay, to the why...
so find-debuginfo fires up multiple threads to split off debuginfo using the
run_job function. rpm runs scripts usually with "-e",
so aborts subscripts on error. now if for some reason the debug-splitting tool
fails, that job will abort.
Now if you have 8 files that are problematic in the tree, and you have 8 or
less jobs, the find-debuginfo will abort as no single
res.$number has been written. If you happen to have more than 8 jobs, the build
will succeed, which makes the whole process
somewhat random.
If you really want to abort on encountering errors in the debug split, this
would need to be done differently, but here this is just
to get some consistency, regardless on the number of jobs used,
I hope that scheds some light on the idea behind the patch.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1391#issuecomment-706168098
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
