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 steve.dower
Recipients dstufft, eric.araujo, paul.moore, steve.dower, terry.reedy, tim.golden, vstinner, zach.ware
Date 2016-08-17.22:47:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1471474058.08.0.670548879312.issue27790@psf.upfronthosting.co.za>
In-reply-to
Content
It certainly looks like more than we used to get...

Ideally we'd capture the output from the build process and only write it out if the test failed. I'm not entirely sure why that isn't happening here. The warnings themselves are harmless (you get a nearly identical warning if you *don't* put /LTCG on the command line and need it - I'd guess there was a stalemate between two factions on the compiler team at some point and they resolved it with this warning).
History
Date User Action Args
2016-08-17 22:47:38steve.dowersetrecipients: + steve.dower, terry.reedy, paul.moore, vstinner, tim.golden, eric.araujo, zach.ware, dstufft
2016-08-17 22:47:38steve.dowersetmessageid: <1471474058.08.0.670548879312.issue27790@psf.upfronthosting.co.za>
2016-08-17 22:47:38steve.dowerlinkissue27790 messages
2016-08-17 22:47:37steve.dowercreate