Skip to content

fix: cluster sanity does not need to execute when operator or cluster health is run #1184

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sheltoncyril merged 1 commit into from
Mar 9, 2026
Merged

fix: cluster sanity does not need to execute when operator or cluster health is run #1184

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions tests/conftest.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -676,6 +676,12 @@ def cluster_sanity_scope_session(
dsc_resource: DataScienceCluster,
junitxml_plugin: Callable[[str, object], None],
) -> None:
# Skip cluster sanity check when running tests that have cluster_health or operator_health markers
selected_markers = {mark.name for item in request.session.items for mark in item.iter_markers()}
if {"cluster_health", "operator_health"} & selected_markers:
LOGGER.info("Skipping cluster sanity check because selected tests include cluster/operator health")
return

verify_cluster_sanity(
request=request,
nodes=nodes,
Expand Down