Marks xfail xgboost test due to scikit lib issue

[skrawcz]

Skips because we're seeing:

AttributeError: 'super' object has no attribute 'sklearn_tags'
due to new library version rolling out and xgboost not being updated yet.

Changes

• mark xfail for flaky test

How I tested this

Notes

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to c2c3b03 in 17 seconds

More details

• Looked at 12 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 2 drafted comments based on config settings.

1. tests/plugins/test_xgboost_extensions.py:37

• Draft comment:
  The xfail mark is applied with condition=True, meaning the test is expected to fail unconditionally. Ensure to revisit this once the library incompatibility is resolved.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The xfail mark is applied with condition=True, which means it will always expect the test to fail. This is appropriate given the PR description, but it should be noted that this is a temporary measure until the library incompatibility is resolved.

2. tests/plugins/test_xgboost_extensions.py:38

• Draft comment:
  Function and method names should follow consistent patterns. Consider renaming test_xgboost_model_json_reader and other test functions to maintain consistency in naming conventions.
• Reason this comment was not posted:
  Comment was on unchanged code.

Workflow ID: wflow_EapOU3s7moOMiY8d

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

❌ Changes requested. Incremental review on 3060b64 in 31 seconds

More details

• Looked at 32 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. tests/test_node.py:63

• Draft comment:
  Consider using more descriptive variable names for major and minor, such as numpy_major_version and numpy_minor_version, to improve code readability. This applies to line 48 as well.
• Reason this comment was not posted:
  Comment was not on a valid diff hunk.

Workflow ID: wflow_EhsVp2uCVlE6onWA

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

The condition sys.version_info > (3, 9) should be sys.version_info >= (3, 9) to correctly include Python 3.9 and above.