Remove `test.test_json.test_tool.TestTool.test_colors` from PGO

[zooba]

Bug report

The test seems to fail a lot during PGO profiling.

It may be fine just to entirely remove test_tool, if it's not really core code paths. Probably worth someone doing the benchmarking here to see if it's useful.

[ashm-dev]

@zooba I compile cpython with pgo quite a lot, and none of my tests have failed if sanitizers are not enabled. So maybe you have some kind of problem with the build?)

[zooba]

Perhaps it's Windows-specific then?

[ashm-dev]

Could be, but I’m on Linux.

[sergey-miryanov]

@zooba I just compiled CPython on windows 11 with pgo. And it compiles fine (if I understand you correctly).

Build succeeded.

PGOMGR : warning PG0188: No .PGC files matching 'X:\Work\cpython\main\PCbuild\amd64\_zoneinfo!*.pgc' were found. [X:\Work\cpython\main\PCbuild\_zoneinfo.vcxproj]
X:\Work\cpython\main\PCbuild\amd64\_zoneinfo.pgd : warning C4961: No profile data was merged into 'X:\Work\cpython\main\PCbuild\amd64\_zoneinfo.pgd', profile-guided optimizations disabled [X:\Work\cpython\main\PCbuild\_zoneinfo.vcxproj]
    2 Warning(s)
    0 Error(s)

Time Elapsed 00:03:42.06

Could you explain what failures you were faced with?

[zooba]

See these logs from the 3.15.0a1 release build: https://dev.azure.com/Python/cpython/_build/results?buildId=165305&view=logs&j=b9a7e24a-1d9b-5019-7703-8e6075dba299&t=339e554d-d1e3-55db-ce3b-12a33950552a

It looks like they're all launching a separate process which is crashing (normally means not handling environment variables properly), but in any case this isn't a useful thing to do for the PGO profile run. So it would be best to skip those tests that are launching a separate process.