Skip to content
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.

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

[Stack 8.16.0-SNAPSHOT] [cloudflare] Failing test daily: system test: default in cloudflare.logpull #10619

Closed
elastic-vault-github-plugin-prod bot opened this issue Jul 27, 2024 · 1 comment · Fixed by #11313
Assignees
Labels
automation flaky-test Unstable or unreliable test cases. Integration:cloudflare Cloudflare Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations]

Comments

@elastic-vault-github-plugin-prod
Copy link

elastic-vault-github-plugin-prod bot commented Jul 27, 2024

  • Stack version: 8.16.0-SNAPSHOT
  • Package: cloudflare
  • Failing test: system test: default
  • DataStream: logpull
  • Owners:
    • @elastic/security-service-integrations

Failure:

test case failed: could not find hits in logs-cloudflare.logpull-87857 data stream

First build failed: https://buildkite.com/elastic/integrations/builds/14060

Latest 5 failed builds:

@elastic-vault-github-plugin-prod elastic-vault-github-plugin-prod bot added automation flaky-test Unstable or unreliable test cases. labels Jul 27, 2024
@andrewkroh andrewkroh added Integration:cloudflare Cloudflare Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations] labels Aug 2, 2024
@chrisberkhout chrisberkhout self-assigned this Sep 2, 2024
@chrisberkhout
Copy link
Contributor

Everything passes locally against the same stack version.

It's always the default case of the system tests for the logpull data stream. That case brings up the logpull-mock-service container, which runs a Go program.

There may be a problem with using the mock before it's really ready to answer requests.

If so, it may help to shorten the interval time from 1h to 2m, and it should be properly resolved by adding a health check as was done for a different package in #9926.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation flaky-test Unstable or unreliable test cases. Integration:cloudflare Cloudflare Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations]
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants