Author neyuru
Recipients neyuru, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-01-19.07:03:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Mmm, I don't find that option documented in the readme of the MSI folder nor in the help for buildrelease.bat (and also is not intuitive, what does IIRC stand for?), nevertheless:

It should be no problem if this PR doesn't pass but it should help newcomers like me to debug builds (the option -q is also not documented in the buildrelease but I found that option tracking the build calls all the way to I leave this info here if anyone benefits from it.

In fact I edited the PGO option in the buildrelease file to:

PGO= -m test --pgo -uall -j8 -M 27Gb -x test_bigmem test_bz2 test_codecs test_httpservers test_nntplib test_platform test_regrtest test_sysconfig test_zlib

The test suite now reads: PASS (I know, it is not necessary for all the tests to pass, but it is a nice view IMO). The benefit of the -j option is  that it permits some tests to pass when they where failing before this option. The option -uall opens resources to the tests, so that some of them will no longer be denied to tests (and therefore leaving no tests run -or skipped- by lack of resources). The 27Gb memory "allocated" to the tests is overkill, but my system could handle it (it may be that some tests need more than that but I have no further memory). 

Sure, it takes a long time to build (close to 1 hr) but it is the best way I have found so far to minimize the number of failed tests: with this option, only those 9 tests fail out of the 407 in Python 3.6 This info was found by disabling the quiet option, so that is another plus.

If you have time, can I ask a question related to the *.pgc files?
Date User Action Args
2019-01-19 07:03:20neyurusetrecipients: + neyuru, paul.moore, tim.golden, zach.ware, steve.dower
2019-01-19 07:03:19neyurusetmessageid: <>
2019-01-19 07:03:19neyurulinkissue35739 messages
2019-01-19 07:03:19neyurucreate