Skip to content

Trigger Test: Use container log streams instead of DB reads#22502

Draft
DylanTinianov wants to merge 2 commits into
developfrom
CRE-4359-fix-flaky-trigger-test
Draft

Trigger Test: Use container log streams instead of DB reads#22502
DylanTinianov wants to merge 2 commits into
developfrom
CRE-4359-fix-flaky-trigger-test

Conversation

@DylanTinianov
Copy link
Copy Markdown
Contributor

@DylanTinianov DylanTinianov commented May 15, 2026

Fixes flaky trigger test by using container log streams instead of relying on DB inserts/ deletes.

@DylanTinianov DylanTinianov self-assigned this May 15, 2026
@DylanTinianov DylanTinianov changed the title Flaky Test: Use container log stream instead of DB reads Trigger Test: Use container log stream instead of DB reads May 15, 2026
@DylanTinianov DylanTinianov changed the title Trigger Test: Use container log stream instead of DB reads Trigger Test: Use container log streams instead of DB reads May 15, 2026
@github-actions
Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@cl-sonarqube-production
Copy link
Copy Markdown

@trunk-io
Copy link
Copy Markdown

trunk-io Bot commented May 15, 2026

Static BadgeStatic BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant