Mark a few cuml-accel upstream tests as flaky

[jcrist]

These tests match based on time in the logs, and can sometimes fail if an operation takes longer (possibly due to CI contention issues).

Fixes #7962

[jcrist]

I've seen at least one of these fail locally before. That and the fact that test_random_search_cv_results_multimetric was already marked as flaky makes me think this is less of a regression and more of us finally catching (and noting!) a failure for these.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d115a613-7aa7-4139-8398-0f3d21c40941

📥 Commits

Reviewing files that changed from the base of the PR and between de94966 and b0e9fda.

📒 Files selected for processing (1)

• python/cuml/cuml_accel_tests/upstream/scikit-learn/xfail-list.yaml

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated test configuration with additional expected test behavior entries to reflect scikit-learn compatibility handling.

Walkthrough

The PR extends the xfail list configuration to mark specific flaky scikit-learn tests as expected failures. Four new test entries are added for timing-sensitive tests that fail intermittently in slow CI environments.

Changes

Cohort / File(s)	Summary
xfail-list configuration python/cuml/cuml_accel_tests/upstream/scikit-learn/xfail-list.yaml	Added four new xfail entries: one for test_grid_search_cv_results_multimetric and three for test_fit_and_score_verbosity test variants with parameterized selectors to handle flaky timing-related assertion failures.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• #7962: This PR directly addresses the flaky test failures described in the issue by marking test_grid_search_cv_results_multimetric and test_fit_and_score_verbosity as expected failures due to strict timing assertions in slow CI environments.

Suggested labels

Cython / Python, non-breaking

Suggested reviewers

• viclafargue
• csadorf

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: marking upstream tests as flaky due to timing issues.
Description check	✅ Passed	The description directly relates to the changeset, explaining that tests are flaky due to timing assumptions and referencing issue #7962.
Linked Issues check	✅ Passed	The PR successfully addresses the objective of marking flaky timing-sensitive tests by adding them to the xfail list, directly resolving the issues documented in #7962.
Out of Scope Changes check	✅ Passed	All changes are in-scope: the xfail-list.yaml modification adds only the flaky tests mentioned in issue #7962 without extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jcrist]

/merge