Split CPU unit tests into halves with per-half timeouts

Both full-suite attempts wedge before printing a summary: once the
100th failure trips PYTEST_OPTS' --maxfail, pytest-xdist's interrupt
path stalls forever in mp pool teardown (no timeout guards _close_pool),
and the 6h job limit cancels the run. Run the suite as two fresh-worker
halves, override maxfail so all failures are listed, and cap each half
with timeout so the sequential tail always runs.

Signed-off-by: Guokai Ma <guokai.ma@intel.com>

Author: delock

.github/workflows/cpu-torch-latest.yml

@@ -284,5 +284,12 @@ jobs:
         run: |
           unset TORCH_CUDA_ARCH_LIST # only jit compile for current arch
           cd tests
-          HF_HOME=/tmp/hf_home/ pytest $PYTEST_OPTS --forked -n 4 unit/ --torch_ver="$TORCH_TEST_VERSION"
-          HF_HOME=/tmp/hf_home/ pytest $PYTEST_OPTS --forked -m 'sequential' unit/ --torch_ver="$TORCH_TEST_VERSION"
+          # The suite is split so each half gets fresh xdist workers: multi-rank pool
+          # teardown eventually wedges a worker, and one 3400-test process never
+          # reaches its summary inside the 6h job limit. maxfail is raised so every
+          # failure is listed, and timeout caps each half.
+          overall=0
+          timeout 150m pytest $PYTEST_OPTS --maxfail=100000 --forked -n 4 unit/ --ignore=unit/v1 --torch_ver="$TORCH_TEST_VERSION" || overall=$?
+          timeout 150m pytest $PYTEST_OPTS --maxfail=100000 --forked -n 4 unit/v1 --torch_ver="$TORCH_TEST_VERSION" || overall=$?
+          HF_HOME=/tmp/hf_home/ pytest $PYTEST_OPTS --forked -m 'sequential' unit/ --torch_ver="$TORCH_TEST_VERSION" || overall=$?
+          exit $overall