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.

Sign up for GitHub

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

Jump to bottom

Build 799 for main with status FAILURE #32814

Closed
Tracked by #15
elasticmachine opened this issue Aug 24, 2022 · 4 comments · Fixed by #32785
Closed
Tracked by #15

Build 799 for main with status FAILURE #32814

elasticmachine opened this issue Aug 24, 2022 · 4 comments · Fixed by #32785
Assignees
@rdner
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 v8.5.0

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: 2022-08-24T14:16:50.268+0000

  • Duration: 79 min 14 sec

Test stats 🧪

Test Results
Failed 2
Passed 22598
Skipped 1899
Total 24499

Test errors 2

Expand to view the tests failures

Build&Test / libbeat-unitTest / TestPublish/cancel_the_batch_when_a_different_server_responds – github.com/elastic/beats/v7/libbeat/outputs/shipper
    Expand to view the error details

     Failed

    Expand to view the stacktrace

     === RUN   TestPublish/cancel_the_batch_when_a_different_server_responds
    shipper_test.go:423: 
        	Error Trace:	shipper_test.go:423
        	Error:      	Condition never satisfied
        	Test:       	TestPublish/cancel_the_batch_when_a_different_server_responds
    --- FAIL: TestPublish/cancel_the_batch_when_a_different_server_responds (0.12s)

Build&Test / libbeat-unitTest / TestPublish – github.com/elastic/beats/v7/libbeat/outputs/shipper
    Expand to view the error details

     Failed

    Expand to view the stacktrace

     === RUN   TestPublish
--- FAIL: TestPublish (2.12s)

Steps errors 5

Expand to view the steps failures

libbeat-unitTest - mage build unitTest
  • Took 3 min 36 sec . View more details here
  • Description: mage build unitTest
libbeat-unitTest - mage build unitTest
  • Took 1 min 54 sec . View more details here
  • Description: mage build unitTest
libbeat-unitTest - mage build unitTest
  • Took 1 min 54 sec . View more details here
  • Description: mage build unitTest
metricbeat-goIntegTest - mage goIntegTest
  • Took 29 min 22 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 Aug 24, 2022
@elasticmachine
Copy link
Collaborator Author

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

@cmacknz cmacknz added the v8.5.0 label Aug 24, 2022
@cmacknz
Copy link
Member

cmacknz commented Aug 24, 2022

@rdner looks like the shipper tests might be Flaky

@cmacknz
Copy link
Member

cmacknz commented Aug 24, 2022 •
edited
Loading

Here's some other occurrences

@cmacknz cmacknz mentioned this issue Aug 24, 2022
Closed
29 tasks
@rdner
Copy link
Member

rdner commented Aug 25, 2022

@cmacknz merging #32785 should solve the problem

@cmacknz cmacknz mentioned this issue Aug 29, 2022
Merged
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rdner rdner

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 v8.5.0
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make event acknowledgment asynchronous in shipper output rdner/beats
3 participants
@rdner @cmacknz @elasticmachine