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

[reporting] disable surprisingly failing test #26738

Merged

Conversation

spalger
Copy link
Contributor

@spalger spalger commented Dec 5, 2018

These tests started failing on master seemingly out of nowhere, and they're tricky to debug so we are disabling them in master so that @tsullivan has time to debug and fix them.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@tsullivan
Copy link
Member

The chromium tests failed because of the reason we're looking into

image

@spalger spalger force-pushed the disable-surprisingly-failing-test branch from b5c25c6 to 586f9e6 Compare December 6, 2018 01:37
@elasticmachine

This comment has been minimized.

Copy link
Member

@tsullivan tsullivan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

This is a lot to turn off. I'm looking into the failures

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@joelgriffith
Copy link
Contributor

I was in the middle of a git bisect workflow. Having pegged 83325bf560 as good. I’m happy to jump back in tomorrow AM since I’m out

@joelgriffith joelgriffith merged commit d3f0db3 into elastic:master Dec 6, 2018
@tsullivan
Copy link
Member

tsullivan commented Dec 6, 2018

I'm working on adding more logging on the download route handler, to show the reason why the requested report failed:

? proc [kibana] server log [17:25:12.218] [error][download][reporting] Report jpcvg4q916nha0f068ef44p5 has non-OK status: [500] Reason: [{"message":"Reporting generation failed","reason":"Error: Phantom exited with code: null. Your report may be too large. Try removing some visualizations or increasing the RAM available to Kibana."}]

Still needs investigation

tsullivan pushed a commit to tsullivan/kibana that referenced this pull request Dec 12, 2018
* [reporting] disable surprisingly failing test

* fix expected completion count

* quit chasing, just exclude these configs
tsullivan added a commit that referenced this pull request Dec 13, 2018
* [reporting] disable surprisingly failing test

* fix expected completion count

* quit chasing, just exclude these configs
@spalger spalger deleted the disable-surprisingly-failing-test branch August 18, 2020 17:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants