My 'make check' runs valgrind a bunch of times. Right now, each invocation is sitting and doing nothing for about ten minutes, before it apparently times out downloading something from debuginfod.fedoraproject.org:
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 0 (Timeout)
poll([{fd=9, events=POLLIN}], 1, 1000) = 0 (Timeout)
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAND}], 1, 0) = 0 (Timeout)
poll([{fd=9, events=POLLIN}], 1, 1000) = 0 (Timeout)
poll([{fd=9, events=POLLIN|POLLPRI|POLLRDNORM|POLLRDBAN
Whether using valgrind or gdb, I find that debuginfod gets stuck more often
than not, and this is getting old. I don't know what it's beef is. I can
reach debuginfod.fedoraproject.org on port 443 without any issues.
After perusing the man page I set DEBUGINFOD_MAXTIME=10, and things are slowly, slowly moving forward. But I'm wondering if anyone found debuginfod to be reliable.
Attachment:
pgpBX4fIHz8vg.pgp
Description: PGP signature
-- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
