Skip to content
Merged
Changes from all commits
Commits
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
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Using pytest_collection_modifyitems is a bit overkill here I would say:

pytestmark = pytest.mark.skipif(
    date.today() < _SKIP_UNTIL,
    reason=f"Hosted extractor integration tests are flaky; skip until {_SKIP_UNTIL.isoformat()}"
)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Another comment, based on the Slack feedback, https://cognitedata.slack.com/archives/C065WLH4G5N/p1776687620276759?thread_ts=1776677363.910429&cid=C065WLH4G5N , we should modify our test setup - the error message we suddenly started getting is the "correct" API response.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Did it myself 😉

Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ def cleanup_stale_test_sources(cognite_client: CogniteClient) -> None:
and now_ms - s.created_time >= 3 * 60 * 60 * 1000 # type: ignore [attr-defined]
]
if stale:
cognite_client.hosted_extractors.sources.delete(stale, ignore_unknown_ids=True)
cognite_client.hosted_extractors.sources.delete(stale, force=True, ignore_unknown_ids=True)


@pytest.fixture
Expand Down
Loading