test: skip 8 integration tests broken by test-org fixture drift#611
Merged
nathantournant merged 1 commit intoJul 7, 2026
Merged
Conversation
riyazsh
force-pushed
the
riyaz/skip-preexisting-broken-integration-tests
branch
from
July 6, 2026 18:36
dc346cf to
9ecfc33
Compare
Extends existing skip pattern used elsewhere in these files: - test_logs_archives: sync/update_sync (S3 bucket in test org missing) - test_logs_archives_order: sync (depends on above) - test_metric_tag_configurations: import (test org has no tag configs) These have been failing on scheduled main runs for days. Unblocks the test-integrations job while the fixture is repaired.
riyazsh
force-pushed
the
riyaz/skip-preexisting-broken-integration-tests
branch
from
July 6, 2026 18:49
9ecfc33 to
ba2b9a7
Compare
nathantournant
approved these changes
Jul 7, 2026
gh-worker-dd-devflow-36fce6
Bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
nathantournant
deleted the
riyaz/skip-preexisting-broken-integration-tests
branch
July 7, 2026 08:39
gh-worker-dd-devflow-36fce6
Bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Marks 8 integration tests as `@pytest.mark.skip` — they have been failing consistently on scheduled `main` runs for the past several days due to test-org fixture drift, not code regressions.
Failing tests + root causes
Evidence
```
ERROR datadog_sync_cli [logs_archives - 4n70c12NSSOIa5fhDTUCNg]
400 Bad Request - {"errors":["Bucket does not exist on AWS S3"]}
```
Approach
Extends the existing `@pytest.mark.skip` pattern already used in these files (e.g. `test_logs_archives.py` already skips `test_resource_import*` with reason "require an AWS, GCP, or Azure account"). Skip reasons here call out the specific test-org fixture problem so the tests can be unskipped once fixtures are restored.
Why now
Unblocks the `test-integrations` check for all in-flight PRs (e.g. #602). No test coverage lost — these tests weren't providing signal anyway; they've been failing every run for 4+ days.
Test plan