Message 346512 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	koobs
Recipients	koobs, vstinner
Date	2019-06-25.11:25:12
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1561461913.18.0.413597174764.issue37400@roundup.psfhosted.org>
In-reply-to

Content
And I just remembered that I had to restart the build worker service on that host (koobs-freebsd10) this morning as I was receiving messaging that the worker had gone missing. I ran `[koobs@10-STABLE-amd64:~] sudo /usr/local/etc/rc.d/buildslave restart` which is the same as the prevailing reproduction case in #27838 I could restart the worker to make the issue go away, but I think the underlying issue should be fixed instead. Should we close this as a dupe and reopen the original?

And I just remembered that I had to restart the build worker service on that host (koobs-freebsd10) this morning as I was receiving messaging that the worker had gone missing.

I ran `[koobs@10-STABLE-amd64:~] sudo /usr/local/etc/rc.d/buildslave restart`

which is the same as the prevailing reproduction case in #27838

I could restart the worker to make the issue go away, but I think the underlying issue should be fixed instead.

Should we close this as a dupe and reopen the original?

History
Date	User	Action	Args
2019-06-25 11:25:13	koobs	set	recipients: + koobs, vstinner
2019-06-25 11:25:13	koobs	set	messageid: <1561461913.18.0.413597174764.issue37400@roundup.psfhosted.org>
2019-06-25 11:25:13	koobs	link	issue37400 messages
2019-06-25 11:25:12	koobs	create