[issue37707] Skip individual unit tests that are expensive for the PGO task

Neil Schemenauer added the comment: New changeset 382cb85401bb010ead411c0532499ffe16c3cf27 by Neil Schemenauer (Miss Islington (bot)) in branch '3.8': bpo-37707: Exclude expensive unit tests from PGO task (GH-15009) (#15024) https://github.com/python/cpython/commit/382cb85401bb010ead411c05324

[issue37707] Skip individual unit tests that are expensive for the PGO task

Change by Neil Schemenauer : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue37707] Skip individual unit tests that are expensive for the PGO task

Neil Schemenauer added the comment: New changeset 52a48e62c6a94577152f9301bbe5f3bc806cfcf1 by Neil Schemenauer in branch 'master': bpo-37707: Exclude expensive unit tests from PGO task (GH-15009) https://github.com/python/cpython/commit/52a48e62c6a94577152f9301bbe5f3bc806cfcf1 -- _

[issue37707] Skip individual unit tests that are expensive for the PGO task

Change by miss-islington : -- pull_requests: +14786 pull_request: https://github.com/python/cpython/pull/15024 ___ Python tracker ___ __

[issue37707] Skip individual unit tests that are expensive for the PGO task

Change by Neil Schemenauer : -- keywords: +patch pull_requests: +14772 pull_request: https://github.com/python/cpython/pull/15009 ___ Python tracker ___ ___

[issue37707] Skip individual unit tests that are expensive for the PGO task

New submission from Neil Schemenauer : Add a new support decorator, @skip_if_pgo_task and then use it to mark test cases. I suspect the PGO task works well if it can exercise common code paths. Running long tests likely have rapidly diminishing benefits. The instrumented PGO executable run