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 gregory.p.smith
Recipients alex, benjamin.peterson, gregory.p.smith, izbyshev, miss-islington, pablogsal, serhiy.storchaka, twouters
Date 2018-12-31.04:34:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Status on my upcoming buildbot host after today's changes:

== Tests result: FAILURE ==

375 tests OK.

11 tests failed:
    test_asyncio test_builtin test_code test_ctypes test_ioctl
    test_openpty test_os test_posix test_pty test_shutil test_uuid

32 tests skipped:
    test_bz2 test_curses test_dbm_gnu test_dbm_ndbm test_devpoll
    test_gzip test_idle test_kqueue test_lzma test_msilib
    test_ossaudiodev test_readline test_smtpnet test_socketserver
    test_sqlite test_ssl test_startfile test_tcl test_timeout test_tix
    test_tk test_ttk_guionly test_ttk_textonly test_turtle
    test_urllib2net test_urllibnet test_winconsoleio test_winreg
    test_winsound test_xmlrpc_net test_zipfile64 test_zlib

Most of those are dying due to pty use (openpty, etc) which is not properly memory sanitizer traced.  test_posix appears to have something
I can fix by annotating in the code.

after that, I'll decide how to tell my buildbot not to run those tests so we can have a green buildbot memory sanitizing everything else.
Date User Action Args
2018-12-31 04:34:16gregory.p.smithsetrecipients: + gregory.p.smith, twouters, benjamin.peterson, alex, serhiy.storchaka, izbyshev, pablogsal, miss-islington
2018-12-31 04:34:15gregory.p.smithsetmessageid: <>
2018-12-31 04:34:15gregory.p.smithlinkissue35214 messages
2018-12-31 04:34:15gregory.p.smithcreate