You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee=Noneclosed_at=<Date2019-07-30.18:12:56.420>created_at=<Date2019-07-29.18:34:07.203>labels= ['type-feature', 'build']
title='Skip individual unit tests that are expensive for the PGO task'updated_at=<Date2019-07-30.18:34:48.942>user='https://github.com/nascheme'
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 runs quite a bit slower than a normal build and so it is useful to spend a bit of time to exclude expensive tests.