Increase test_timeout on cstratak-*-ppc64le#740
Conversation
`test_tools` has been timing out here. Note the timeout was increased for RHEL8 (i.e. older CPython branches) in python#468; this increases it for the other workers.
|
@stratakis: What do you think of increasing the timeout on the Fedora/RHEL/CentOS ppc64le workers? |
|
The Fedora/RHEL/CentOS ppc64 workers use @stratakis: Do you recall why you chose to use |
The formula I recall using at the time was testing with the same number of CPUs and above that, the whole test suite run was usually faster with 2 more tests above the baseline CPU number. I tested it now and on the c9s ppc64le buildbot which has 8 cores and 8 GB of RAM. For the full test suite on an lto build: The timeout is the correct fix here, test_tools possibly uses a lot of CPU at the time it runs, hence competing with others. |
|
OK, I'll merge this. One question though: do the |
They are shared, although I don't think pinning or isolating would bring too big of a benefit, overall the host is using 40 logical CPUs our of 64 for various VMs. It won't be CPU starved but yeah different vCPUs could be running on the same core. |
test_toolshas been timing out on PPC64LE CentOS9 LTO. Perhaps it's time to increase the timeout.Note the timeout was increased for RHEL8 (i.e. older CPython branches) in #468; this increases it for the other workers.