I thought we did this already, but we don't, except indirectly as part of the profile-guided optimization.
Do we need to do anything above and beyond what PGO does?
Technically those tests are run by a differently compiled binary, so we should run them again with the final binary.
Also, when run as part of PGO, test failures are ignored.
Special call out to asyncio, we should make sure it works properly on Python 3.6.
Run Python self-tests when building interpreter
Activity
theacodes commented on Apr 25, 2017
Do we need to do anything above and beyond what PGO does?
duggelz commented on Apr 25, 2017
Technically those tests are run by a differently compiled binary, so we should run them again with the final binary.
theacodes commented on Apr 25, 2017
duggelz commented on May 5, 2017
Also, when run as part of PGO, test failures are ignored.
Special call out to asyncio, we should make sure it works properly on Python 3.6.
Run Python self-tests when building interpreter
Run Python self-tests when building interpreter