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

Build 1754 for main with status FAILURE - Build&Test / libbeat-goIntegTest / TestTemplateDisabled #36177

Closed
elasticmachine opened this issue Jul 30, 2023 · 3 comments · Fixed by #36187
Assignees
Labels
automation build-failures Build failures in the CI. ci-reported Issues that have been automatically reported from the CI Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Comments

@elasticmachine
Copy link
Collaborator

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-07-30T13:57:52.405+0000

  • Duration: 75 min 24 sec

Test stats 🧪

Test Results
Failed 1
Passed 27592
Skipped 2008
Total 29601

Test errors 1

Expand to view the tests failures

Build&Test / libbeat-goIntegTest / TestTemplateDisabled – github.com/elastic/beats/v7/libbeat/tests/integration
    Expand to view the error details

     Failed 
    

    Expand to view the stacktrace

     === RUN   TestTemplateDisabled
        template_test.go:296: 
            	Error Trace:	/var/lib/jenkins/workspace/main-1754-c7e2a3ab-fdf4-42c7-944a-9225a9ea572c/src/github.com/elastic/beats/libbeat/tests/integration/framework.go:268
            	            				/var/lib/jenkins/workspace/main-1754-c7e2a3ab-fdf4-42c7-944a-9225a9ea572c/src/github.com/elastic/beats/libbeat/tests/integration/template_test.go:296
            	Error:      	Condition never satisfied
            	Test:       	TestTemplateDisabled
        framework.go:352: Temporary directory saved: /var/lib/jenkins/workspace/main-1754-c7e2a3ab-fdf4-42c7-944a-9225a9ea572c/src/github.com/elastic/beats/libbeat/build/integration-tests/TestTemplateDisabled-1690728364
    --- FAIL: TestTemplateDisabled (20.32s)
     
    

Steps errors 4

Expand to view the steps failures

libbeat-goIntegTest - mage goIntegTest
  • Took 8 min 37 sec . View more details here
  • Description: mage goIntegTest
libbeat-goIntegTest - mage goIntegTest
  • Took 4 min 14 sec . View more details here
  • Description: mage goIntegTest
libbeat-goIntegTest - mage goIntegTest
  • Took 4 min 54 sec . View more details here
  • Description: mage goIntegTest
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: Error "hudson.AbortException: script returned exit code 1"

@elasticmachine elasticmachine added automation ci-reported Issues that have been automatically reported from the CI build-failures Build failures in the CI. Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Jul 30, 2023
@elasticmachine
Copy link
Collaborator Author

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@pierrehilbert pierrehilbert changed the title Build 1754 for main with status FAILURE Build 1754 for main with status FAILURE - Build&Test / libbeat-goIntegTest / TestTemplateDisabled Jul 31, 2023
@pierrehilbert
Copy link
Collaborator

As it seems to be related to your migration from Python to Go, could you please have a look @leehinman ?

@leehinman
Copy link
Contributor

I was able to reproduce. Occasionally 2 events get published and we are specifically looking for "PublishEvents: 1 events have been published". I'll get a PR up later today to deal with that.

leehinman added a commit to leehinman/beats that referenced this issue Jul 31, 2023
- test assumed 1 event published, could be multiple
- added LogMatch function to framework to use regexp
- added some more debug info when tests fail, useful in CI where we
  don't always get the directory contents

Closes elastic#36177
leehinman added a commit to leehinman/beats that referenced this issue Jul 31, 2023
- test assumed 1 event published, could be multiple
- added LogMatch function to framework to use regexp
- added some more debug info when tests fail, useful in CI where we
  don't always get the directory contents

Closes elastic#36177
leehinman added a commit to leehinman/beats that referenced this issue Jul 31, 2023
- test assumed 1 event published, could be multiple
- added LogMatch function to framework to use regexp
- added some more debug info when tests fail, useful in CI where we
  don't always get the directory contents

Closes elastic#36177
leehinman added a commit to leehinman/beats that referenced this issue Aug 3, 2023
- test assumed 1 event published, could be multiple
- added LogMatch function to framework to use regexp
- added some more debug info when tests fail, useful in CI where we
  don't always get the directory contents

Closes elastic#36177
leehinman added a commit to leehinman/beats that referenced this issue Aug 3, 2023
- test assumed 1 event published, could be multiple
- added LogMatch function to framework to use regexp
- added some more debug info when tests fail, useful in CI where we
  don't always get the directory contents

Closes elastic#36177
leehinman added a commit that referenced this issue Aug 4, 2023
* fix flaky integration tests

- test assumed 1 event published, could be multiple
- added LogMatch function to framework to use regexp
- added some more debug info when tests fail, useful in CI where we
  don't always get the directory contents

Closes #36177
Scholar-Li pushed a commit to Scholar-Li/beats that referenced this issue Feb 5, 2024
* fix flaky integration tests

- test assumed 1 event published, could be multiple
- added LogMatch function to framework to use regexp
- added some more debug info when tests fail, useful in CI where we
  don't always get the directory contents

Closes elastic#36177
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation build-failures Build failures in the CI. ci-reported Issues that have been automatically reported from the CI Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants