Swap mesos_master and control_m test exceptions to agnostic http_exceptions hierarchy

[mwdd146980]

What does this PR do?

Moves the mesos_master and control_m test suites off requests.exceptions and onto the backend-agnostic http_exceptions hierarchy, so their assertions no longer name a backend-specific exception type and stay green once these integrations move to httpx2.

requests' HTTPError is a status error, so it maps to HTTPStatusError (the leaf), not the agnostic HTTPError root. Both integrations are safe to swap now because each injects the exception through a mock and production already catches the agnostic type (mesos_master.py:187) or catches Exception and re-raises (control_m/check.py).

Motivation

Part of the requests to httpx2 migration. Decoupling these assertions from requests.exceptions lets the suites pass under either backend, ahead of the per-integration flip.

Verification

• ddev --no-interactive test mesos_master: 17 passed, 1 e2e skipped.
• ddev --no-interactive test control_m: 28 passed.
• ddev test -fs mesos_master control_m: clean.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[datadog-prod-us1-5]

   

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 4 Pipeline jobs failed

PR | test / test-minimum-base-package (linux, ubuntu-22.04, control_m, Control-M (py3.13), py3.13) / minimum-base-package-Control-M (py3.13)-py3.13     

PR | test / test-minimum-base-package (linux, ubuntu-22.04, mesos_master, Mesos Master (py3.13-1.7), py3.13-1.7) / minimum-base-package-Mesos Master (py3.13-1.7)-py3.13-1.7     

Validate repository | Run Validations / Validate     

View all 4 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 87.90% (-0.31%)

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 1ec9e81 | Docs | Datadog PR Page | Give us feedback!}

[mwdd146980]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

integrations-core/mesos_master/datadog_checks/mesos_master/mesos_master.py

Line 16 in 290af0a

from datadog_checks.base.utils.http_exceptions import HTTPTimeoutError

Bump the base dependency for HTTPTimeoutError

This new production import relies on the newer datadog_checks.base.utils.http_exceptions module, but mesos_master/pyproject.toml:31 still allows datadog-checks-base>=37.33.0. In standalone installs that resolve one of those still-allowed older base versions, importing datadog_checks.mesos_master will fail before the check can run; please raise the minimum base dependency alongside this import.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 290af0a8a2

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[dd-octo-sts]

Validation Report

Validation	Description	Status
dep	Verify dependency pins are consistent and Agent-compatible	❌

Run ddev validate all changed --fix to attempt to auto-fix supported validations.

Passed validations (20)

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run