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 Michael.Felt
Recipients David.Edelsohn, Michael.Felt, vstinner
Date 2019-04-12.08:28:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <65979085-a569-95d0-77b9-68e6baa76436@felt.demon.nl>
In-reply-to <1554914943.12.0.570465891658.issue36579@roundup.psfhosted.org>
Content
On 10/04/2019 18:49, STINNER Victor wrote:
> STINNER Victor <vstinner@redhat.com> added the comment:
>
> "I am looking into this - but as it seems to have gone away again - is
> there a simple way to get that code back, and/or see what the diff is,
> before/badrun/after?"
>
> Maybe it's just a flacky test. It's hard to guess.
>
> You can get the Git revision of a build by looking at details:
>
> https://buildbot.python.org/all/#/builders/10/builds/2389
> => Properties: "got_revision: 8702b67dad62a9084f6c1823dce10653743667c8"
>
> See also "Changes" tab.
>
> Sometimes when a bug disappears, I just close it as "outdated" after a few weeks.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue36579>
> _______________________________________
>
I'll try a manual build on the gccfarm. Not exactly the same
environment, but as close as I can get.
History
Date User Action Args
2019-04-12 08:28:32Michael.Feltsetrecipients: + Michael.Felt, vstinner, David.Edelsohn
2019-04-12 08:28:32Michael.Feltlinkissue36579 messages
2019-04-12 08:28:32Michael.Feltcreate