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 nascheme
Recipients gregory.p.smith, nascheme, vstinner
Date 2017-11-14.19:56:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510689364.02.0.213398074469.issue31963@psf.upfronthosting.co.za>
In-reply-to
Content
I'm willing to put some time into trying to fix this, in the case that it is caused by my Makefile changes.  However, it would be very helpful if I could login to the build-bot and try running with the Makefile change backed out.  Is that possible?  Having to setup a VM to match the compiler of the build-bot would take quite a bit a of extra time.

Looking at the "stdout" log file, I can't see that we are doing anything wrong.  Specifically, the ".gc??" files are being removed and so I think that rules out the theory of stale profile information files messing up GCC.
History
Date User Action Args
2017-11-14 19:56:04naschemesetrecipients: + nascheme, gregory.p.smith, vstinner
2017-11-14 19:56:04naschemesetmessageid: <1510689364.02.0.213398074469.issue31963@psf.upfronthosting.co.za>
2017-11-14 19:56:04naschemelinkissue31963 messages
2017-11-14 19:56:03naschemecreate