-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] Kibana installs Chromium headless browser when running the integration tests #102919
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Reporting:Framework
Reporting issues pertaining to the overall framework
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:medium
Medium Level of Effort
needs-team
Issues missing a team label
Comments
mshustov
added
bug
Fixes for quality problems that affect the customer experience
Team:Operations
Team label for Operations Team
Team:AppServices
labels
Jun 22, 2021
Pinging @elastic/kibana-app-services (Team:AppServices) |
exalate-issue-sync
bot
added
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:small
Small Level of Effort
labels
Jun 22, 2021
exalate-issue-sync
bot
added
loe:medium
Medium Level of Effort
and removed
loe:small
Small Level of Effort
labels
Jun 22, 2021
today I had a false positive test failure due to this problem
https://github.com/elastic/kibana/pull/107130/checks?check_run_id=3199236871 cc @elastic/kibana-operations |
tsullivan
changed the title
Kibana installs headless browser when running the integration tests
[Reporting] Kibana installs Chromium headless browser when running the integration tests
Aug 2, 2021
tylersmalley
removed
loe:medium
Medium Level of Effort
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
EnableJiraSync
labels
Mar 16, 2022
exalate-issue-sync
bot
added
impact:needs-assessment
Product and/or Engineering needs to evaluate the impact of the change.
loe:medium
Medium Level of Effort
labels
Mar 30, 2022
exalate-issue-sync
bot
added
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
and removed
impact:needs-assessment
Product and/or Engineering needs to evaluate the impact of the change.
labels
Apr 11, 2022
It seems this is no longer an issue. I am closing this to take it off our tracker. |
sophiec20
added
the
Feature:Reporting:Framework
Reporting issues pertaining to the overall framework
label
Aug 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Reporting:Framework
Reporting issues pertaining to the overall framework
impact:low
Addressing this issue will have a low level of impact on the quality/strength of our product.
loe:medium
Medium Level of Effort
needs-team
Issues missing a team label
Kibana version: master
PR #102782 failed CI on the
Jest integration tests
step with:which is caused by reporting plugin logging after Kibana stops.
There are 2 problems:
I fixed the problem by disabling the
reporting
plugin in this specific case, but it's rather a workaround.@elastic/kibana-reporting-services is it possible to install a browser in dev mode by a request?
if no, @elastic/kibana-operations should we disable the
reporting
plugin by default in all the integration tests withoss: false
? tbh, I'd like to avoid that because it means dev and test configuration diverge.The text was updated successfully, but these errors were encountered: