Skip to content

ModelCatalog: update default tests to reflect expected behavior#578

Merged
dbasunag merged 3 commits intoopendatahub-io:mainfrom
dbasunag:update_mc_tests
Sep 3, 2025
Merged

ModelCatalog: update default tests to reflect expected behavior#578
dbasunag merged 3 commits intoopendatahub-io:mainfrom
dbasunag:update_mc_tests

Conversation

@dbasunag
Copy link
Copy Markdown
Collaborator

@dbasunag dbasunag commented Sep 2, 2025

Add validations for default resources, update configmap and api test

Description

How Has This Been Tested?

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Summary by CodeRabbit

  • Tests
    • Broadened model catalog coverage with resource-agnostic validations across core components (Deployment, Route, Service, Pod).
    • Added reusable test helpers to verify resource presence and validate default catalog content.
    • Simplified setup by removing unused fixtures and aligning tests to dynamic validation.
    • Updated expectations to assert default catalog presence and adjusted default catalog path.
    • Added a test to verify absence of the default catalog in a temporary scenario.
    • Renamed a test suite for clearer intent.

@dbasunag dbasunag requested review from fege and lugi0 as code owners September 2, 2025 22:38
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Sep 2, 2025

📝 Walkthrough

Walkthrough

Renames a custom catalog test class and reduces fixtures; significantly rewrites default catalog tests to validate resources and ConfigMap contents via DynamicClient and parameterization; adds constants and two test utility validators for resource existence and default catalog structure.

Changes

Cohort / File(s) Summary
Custom catalog tests
tests/model_registry/model_catalog/test_custom_model_catalog.py
Renamed TestModelCatalogRhecTestModelCatalogCustom and removed three fixtures from the usefixtures decorator, leaving model_registry_namespace and updated_catalog_config_map. No other test logic changes.
Default catalog tests
tests/model_registry/model_catalog/test_default_model_catalog.py
Reworked tests to use DynamicClient and parameterized validation across resource kinds (Deployment, Route, Service, Pod). Updated test_config_map_exists to load sources.yaml, require exactly one catalog, and call validate_default_catalog. Added test_default_config_map_not_present and test_model_catalog_resources_exists. Removed dependency on model_registry_metadata_db_resources fixture and adjusted method signatures.
Test utilities
tests/model_registry/model_catalog/utils.py
Added validate_model_catalog_resource(kind, admin_client, namespace) to assert a single labeled resource exists and validate_default_catalog(default_catalog) to assert name/id/type and yamlCatalogPath via constants.
Constants
tests/model_registry/model_catalog/constants.py
Added DEFAULT_CATALOG_NAME, DEFAULT_CATALOG_ID, CATALOG_TYPE, and DEFAULT_CATALOG_FILE with values used by the new validators.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 2, 2025

The following are automatically added/executed:

  • PR size label.
  • Run pre-commit
  • Run tox
  • Add PR author as the PR assignee
  • Build image based on the PR

Available user actions:

  • To mark a PR as WIP, add /wip in a comment. To remove it from the PR comment /wip cancel to the PR.
  • To block merging of a PR, add /hold in a comment. To un-block merging of PR comment /hold cancel.
  • To mark a PR as approved, add /lgtm in a comment. To remove, add /lgtm cancel.
    lgtm label removed on each new commit push.
  • To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
    verified label removed on each new commit push.
  • To Cherry-pick a merged PR /cherry-pick <target_branch_name> to the PR. If <target_branch_name> is valid,
    and the current PR is merged, a cherry-picked PR would be created and linked to the current PR.
  • To build and push image to quay, add /build-push-pr-image in a comment. This would create an image with tag
    pr-<pr_number> to quay repository. This image tag, however would be deleted on PR merge or close action.
Supported labels

{'/build-push-pr-image', '/hold', '/wip', '/lgtm', '/cherry-pick', '/verified'}

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (5)
tests/model_registry/model_catalog/test_custom_model_catalog.py (1)

34-34: Class rename looks good; drop redundant fixture usage and confirm Self typing support

  • The rename to TestModelCatalogCustom is fine.
  • Minor: updated_catalog_config_map is already provided via class-level parametrize and each test’s signature; having it also in @pytest.mark.usefixtures is redundant. Safe to remove from usefixtures to avoid confusion.
  • Ensure the CI Python version is 3.11+. If not, add a typing_extensions fallback for Self in this file.

Apply this diff to remove the redundant fixture in the class-level usefixtures:

 @pytest.mark.usefixtures(
     "model_registry_namespace",
-    "updated_catalog_config_map",
 )
 class TestModelCatalogCustom:

If Python < 3.11 is possible, add this near the imports:

-from typing import Self
+try:
+    from typing import Self
+except ImportError:  # Python < 3.11
+    from typing_extensions import Self  # type: ignore
tests/model_registry/model_catalog/test_default_model_catalog.py (4)

3-8: Ensure compatibility for Self typing on Python < 3.11

If CI isn’t guaranteed to be 3.11+, add a typing_extensions fallback.

Apply this diff:

-from typing import Self, Any
+try:
+    from typing import Self
+except ImportError:  # Python < 3.11
+    from typing_extensions import Self  # type: ignore
+from typing import Any

28-35: ConfigMap test reads well; tiny comment nit

“configmaps is created” → “ConfigMap is created”.

Apply this diff:

-        # Check that the default configmaps is created when model registry is
+        # Check that the default ConfigMap is created when model registry is

65-66: Optionally verify the env var value, not just presence

validate_model_catalog_enabled only checks for the presence of ENABLE_MODEL_CATALOG. Consider also asserting its value is truthy (“true”/“1”).

You can update the helper in utils.py:

-def validate_model_catalog_enabled(pod: Pod) -> bool:
+def validate_model_catalog_enabled(pod: Pod) -> bool:
     for container in pod.instance.spec.containers:
         for env in container.env:
-            if env.name == "ENABLE_MODEL_CATALOG":
-                return True
+            if env.name == "ENABLE_MODEL_CATALOG":
+                val = (env.value or "").strip().lower()
+                return val in {"true", "1", "yes"}
     return False

73-82: Fix assertion message to match what’s being asserted

The message mentions “custom models” while the API here returns sources. Make it explicit that only the default catalog source should exist.

Apply this diff:

-        assert len(result) == 1, f"Expected no custom models to be present. Actual: {result}"
+        assert len(result) == 1, (
+            f"Expected only the default catalog source (no custom catalogs). Actual: {result}"
+        )
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4b221f1 and 5d83b1d.

📒 Files selected for processing (3)
  • tests/model_registry/model_catalog/test_custom_model_catalog.py (1 hunks)
  • tests/model_registry/model_catalog/test_default_model_catalog.py (1 hunks)
  • tests/model_registry/model_catalog/utils.py (1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: dbasunag
PR: opendatahub-io/opendatahub-tests#527
File: tests/model_registry/rbac/conftest.py:358-359
Timestamp: 2025-08-21T19:08:14.982Z
Learning: In tests/model_registry/rbac/conftest.py, the model catalog configmap only exists in one specific namespace (py_config["model_registry_namespace"]) regardless of where model registry instances are deployed, making it a shared resource that serves all model registry instances across namespaces.
📚 Learning: 2025-08-21T19:08:14.982Z
Learnt from: dbasunag
PR: opendatahub-io/opendatahub-tests#527
File: tests/model_registry/rbac/conftest.py:358-359
Timestamp: 2025-08-21T19:08:14.982Z
Learning: In tests/model_registry/rbac/conftest.py, the model catalog configmap only exists in one specific namespace (py_config["model_registry_namespace"]) regardless of where model registry instances are deployed, making it a shared resource that serves all model registry instances across namespaces.

Applied to files:

  • tests/model_registry/model_catalog/utils.py
  • tests/model_registry/model_catalog/test_custom_model_catalog.py
  • tests/model_registry/model_catalog/test_default_model_catalog.py
📚 Learning: 2025-07-17T15:42:23.880Z
Learnt from: lugi0
PR: opendatahub-io/opendatahub-tests#446
File: tests/model_registry/conftest.py:733-770
Timestamp: 2025-07-17T15:42:23.880Z
Learning: In tests/model_registry/conftest.py, the model_registry_instance_1 and model_registry_instance_2 fixtures do not need explicit database dependency fixtures (like db_deployment_1, db_secret_1, etc.) in their function signatures. Pytest's dependency injection automatically handles the fixture dependencies when they reference db_name_1 and db_name_2 parameters. This is the correct pattern for these Model Registry instance fixtures.

Applied to files:

  • tests/model_registry/model_catalog/test_custom_model_catalog.py
🧬 Code graph analysis (2)
tests/model_registry/model_catalog/utils.py (1)
tests/conftest.py (1)
  • admin_client (66-67)
tests/model_registry/model_catalog/test_default_model_catalog.py (4)
tests/model_registry/model_catalog/utils.py (4)
  • validate_model_catalog_enabled (38-43)
  • execute_get_command (29-35)
  • validate_model_catalog_resource (66-69)
  • validate_default_catalog (72-76)
tests/model_registry/model_catalog/conftest.py (2)
  • catalog_config_map (15-16)
  • model_catalog_rest_url (27-36)
tests/conftest.py (1)
  • admin_client (66-67)
tests/model_registry/conftest.py (3)
  • model_registry_namespace (63-64)
  • model_registry_operator_pod (273-280)
  • model_registry_rest_headers (290-295)
🔇 Additional comments (2)
tests/model_registry/model_catalog/utils.py (1)

72-76: Default catalog validation is clear and aligned with expectations

Assertions for name, id, type, and yamlCatalogPath match the intended defaults.

tests/model_registry/model_catalog/test_default_model_catalog.py (1)

59-63: Label assumption verification

This relies on resources labeled component=model-catalog. Confirm the operator consistently applies this label across Deployment/Service/Route/Pod; otherwise the lookup may miss resources.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (6)
tests/model_registry/model_catalog/test_default_model_catalog.py (6)

3-7: Confirm Python version for typing.Self; optionally guard type-only imports.

Self is built-in from Python 3.11+. If CI may run on 3.10, import Self from typing_extensions. Also consider moving DynamicClient under TYPE_CHECKING to avoid runtime dependency for type hints.

Example (no behavior change):

-from kubernetes.dynamic import DynamicClient
+from typing import TYPE_CHECKING
+try:
+    from typing import Self  # py>=3.11
+except Exception:  # pragma: no cover
+    from typing_extensions import Self  # py<=3.10
+if TYPE_CHECKING:
+    from kubernetes.dynamic import DynamicClient

Also applies to: 11-18


28-35: Harden parsing of sources.yaml and improve failure diagnostics.

If safe_load returns None or the key is missing, the test fails with a KeyError/TypeError. Add explicit asserts with clearer messages.

-        catalogs = yaml.safe_load(catalog_config_map.instance.data["sources.yaml"])["catalogs"]
-        assert catalogs
-        assert len(catalogs) == 1, f"{catalog_config_map.name} should have 1 catalog"
+        assert "sources.yaml" in catalog_config_map.instance.data, (
+            f"{catalog_config_map.name} missing 'sources.yaml' key"
+        )
+        data = yaml.safe_load(catalog_config_map.instance.data["sources.yaml"]) or {}
+        assert "catalogs" in data, f"{catalog_config_map.name} 'sources.yaml' missing 'catalogs' section"
+        catalogs = data["catalogs"]
+        assert catalogs, f"{catalog_config_map.name} 'sources.yaml' has empty 'catalogs'"
+        assert len(catalogs) == 1, f"{catalog_config_map.name} should have exactly 1 catalog; got {len(catalogs)}"
         validate_default_catalog(default_catalog=catalogs[0])

37-57: Verify “exactly one resource” assumption, especially for Pods.

validate_model_catalog_resource asserts len == 1 for all kinds. If Pod replicas can be >1, this will be flaky. Either scope the selector more narrowly for Pods or relax the cardinality in the helper to expected_count per kind.


65-66: Clarify assertion message and consider validating the value of ENABLE_MODEL_CATALOG.

The helper only checks presence of the env var. Add an assertion message here; optionally extend the helper to assert truthy value (e.g., "true"/"True").

-        assert validate_model_catalog_enabled(pod=model_registry_operator_pod)
+        assert validate_model_catalog_enabled(pod=model_registry_operator_pod), (
+            "ENABLE_MODEL_CATALOG env var missing or disabled on MR operator pod"
+        )

80-81: Tighten API assertion messaging and validate the default catalog shape.

Message says “no custom models” while asserting len == 1; make it explicit and also validate the default catalog fields returned by the API.

-        assert result
-        assert len(result) == 1, f"Expected no custom models to be present. Actual: {result}"
+        assert result, f"No sources returned from {model_catalog_rest_url[0]}sources"
+        assert len(result) == 1, f"Expected exactly 1 source (default); got {len(result)}: {result}"
+        validate_default_catalog(default_catalog=result[0])

83-87: Pass admin_client to ConfigMap for consistency; consider gating this temporary test.

Instantiate ConfigMap with the fixture client to mirror other tests and avoid implicit global client resolution. Since this is temporary (RHOAIENG-33246), add a skip/xfail guard tied to release or env to prevent future flakiness.

-    def test_default_config_map_not_present(self: Self, model_registry_namespace: str):
+    def test_default_config_map_not_present(self: Self, admin_client: DynamicClient, model_registry_namespace: str):
@@
-        cfg_map = ConfigMap(name="default-model-catalog", namespace=model_registry_namespace)
+        cfg_map = ConfigMap(name="default-model-catalog", client=admin_client, namespace=model_registry_namespace)
         assert not cfg_map.exists, f"{cfg_map.name} should not exist"

Option: mark with skipif based on a release/env flag until 2.25 is broadly available.

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 5d83b1d and d2f172e.

📒 Files selected for processing (3)
  • tests/model_registry/model_catalog/test_custom_model_catalog.py (1 hunks)
  • tests/model_registry/model_catalog/test_default_model_catalog.py (1 hunks)
  • tests/model_registry/model_catalog/utils.py (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • tests/model_registry/model_catalog/test_custom_model_catalog.py
  • tests/model_registry/model_catalog/utils.py
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-08-21T19:08:14.982Z
Learnt from: dbasunag
PR: opendatahub-io/opendatahub-tests#527
File: tests/model_registry/rbac/conftest.py:358-359
Timestamp: 2025-08-21T19:08:14.982Z
Learning: In tests/model_registry/rbac/conftest.py, the model catalog configmap only exists in one specific namespace (py_config["model_registry_namespace"]) regardless of where model registry instances are deployed, making it a shared resource that serves all model registry instances across namespaces.

Applied to files:

  • tests/model_registry/model_catalog/test_default_model_catalog.py
🧬 Code graph analysis (1)
tests/model_registry/model_catalog/test_default_model_catalog.py (4)
tests/model_registry/model_catalog/utils.py (4)
  • validate_model_catalog_enabled (38-43)
  • execute_get_command (29-35)
  • validate_model_catalog_resource (66-69)
  • validate_default_catalog (72-76)
tests/model_registry/model_catalog/conftest.py (2)
  • catalog_config_map (15-16)
  • model_catalog_rest_url (27-36)
tests/conftest.py (1)
  • admin_client (66-67)
tests/model_registry/conftest.py (3)
  • model_registry_namespace (63-64)
  • model_registry_operator_pod (273-280)
  • model_registry_rest_headers (290-295)
🔇 Additional comments (1)
tests/model_registry/model_catalog/test_default_model_catalog.py (1)

58-63: LGTM: shared validator use keeps tests DRY.

@github-actions github-actions bot added size/l and removed size/m labels Sep 3, 2025
@dbasunag
Copy link
Copy Markdown
Collaborator Author

dbasunag commented Sep 3, 2025

/build-push-pr-image

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 3, 2025

Status of building tag pr-578: success.
Status of pushing tag pr-578 to image registry: success.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

♻️ Duplicate comments (1)
tests/model_registry/model_catalog/utils.py (1)

72-76: Don’t assert exactly one Pod; allow >=1 and improve diagnostics.

Pods can scale. Keep strict singleton for other resources; also add clearer failure messages and a reusable label selector.

Per our retrieved learning, the Model Catalog ConfigMap is shared and only exists in py_config["model_registry_namespace"]; ensure callers pass that namespace when validating the ConfigMap.

-def validate_model_catalog_resource(kind: Any, admin_client: DynamicClient, namespace: str) -> None:
-    resource = list(kind.get(namespace=namespace, label_selector="component=model-catalog", dyn_client=admin_client))
-    assert resource
-    assert len(resource) == 1, f"Unexpected number of {kind} resources found: {[res.name for res in resource]}"
+def validate_model_catalog_resource(kind: Any, admin_client: DynamicClient, namespace: str) -> None:
+    label_selector = "component=model-catalog"
+    resources = list(
+        kind.get(namespace=namespace, label_selector=label_selector, dyn_client=admin_client)
+    )
+    kind_name = getattr(kind, "__name__", str(kind))
+    assert resources, f"No {kind_name} found in {namespace} with label '{label_selector}'"
+    if issubclass(kind, Pod):
+        assert len(resources) >= 1, f"Expected at least 1 Pod, found {[res.name for res in resources]}"
+    else:
+        assert len(resources) == 1, f"Unexpected number of {kind_name}: {[res.name for res in resources]}"
🧹 Nitpick comments (2)
tests/model_registry/model_catalog/constants.py (1)

41-44: Name clarity: prefer DEFAULT_CATALOG_TYPE over generic CATALOG_TYPE.

CATALOG_TYPE can be ambiguous alongside other catalog types defined above; DEFAULT_CATALOG_TYPE better communicates scope. Not a blocker.

tests/model_registry/model_catalog/utils.py (1)

78-82: Type hint and add assertion messages for faster triage.

Small tweaks make failures self-explanatory and resilient to missing keys.

-def validate_default_catalog(default_catalog) -> None:
-    assert default_catalog["name"] == DEFAULT_CATALOG_NAME
-    assert default_catalog["id"] == DEFAULT_CATALOG_ID
-    assert default_catalog["type"] == CATALOG_TYPE
-    assert default_catalog["properties"].get("yamlCatalogPath") == DEFAULT_CATALOG_FILE
+def validate_default_catalog(default_catalog: dict[str, Any]) -> None:
+    assert default_catalog.get("name") == DEFAULT_CATALOG_NAME, f"name mismatch: {default_catalog.get('name')!r}"
+    assert default_catalog.get("id") == DEFAULT_CATALOG_ID, f"id mismatch: {default_catalog.get('id')!r}"
+    assert default_catalog.get("type") == CATALOG_TYPE, f"type mismatch: {default_catalog.get('type')!r}"
+    props = default_catalog.get("properties") or {}
+    assert props.get("yamlCatalogPath") == DEFAULT_CATALOG_FILE, f"yamlCatalogPath mismatch: {props.get('yamlCatalogPath')!r}"
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between d2f172e and 1d11e02.

📒 Files selected for processing (2)
  • tests/model_registry/model_catalog/constants.py (1 hunks)
  • tests/model_registry/model_catalog/utils.py (2 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-08-21T19:08:14.982Z
Learnt from: dbasunag
PR: opendatahub-io/opendatahub-tests#527
File: tests/model_registry/rbac/conftest.py:358-359
Timestamp: 2025-08-21T19:08:14.982Z
Learning: In tests/model_registry/rbac/conftest.py, the model catalog configmap only exists in one specific namespace (py_config["model_registry_namespace"]) regardless of where model registry instances are deployed, making it a shared resource that serves all model registry instances across namespaces.

Applied to files:

  • tests/model_registry/model_catalog/utils.py
🧬 Code graph analysis (1)
tests/model_registry/model_catalog/utils.py (1)
tests/conftest.py (1)
  • admin_client (68-69)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build
🔇 Additional comments (2)
tests/model_registry/model_catalog/constants.py (1)

41-44: Centralizing default-catalog expectations via typed constants looks good.

This removes literals from tests and makes expectations explicit and reusable.

tests/model_registry/model_catalog/utils.py (1)

12-17: Good move replacing literals with shared constants.

This addresses prior feedback to avoid hardcoded strings and keeps tests aligned with expected defaults.

Copy link
Copy Markdown
Contributor

@fege fege left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@dbasunag dbasunag merged commit a49ee47 into opendatahub-io:main Sep 3, 2025
11 checks passed
@dbasunag dbasunag deleted the update_mc_tests branch September 3, 2025 15:03
@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 3, 2025

Status of building tag latest: success.
Status of pushing tag latest to image registry: success.

Ygnas pushed a commit to Ygnas/opendatahub-tests that referenced this pull request Sep 4, 2025
…datahub-io#578)

* ModelCatalog: update default tests to reflect expected behavior

* review comments
mwaykole pushed a commit to mwaykole/opendatahub-tests that referenced this pull request Jan 23, 2026
…datahub-io#578)

* ModelCatalog: update default tests to reflect expected behavior

* review comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants