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

Failing test: Chrome UI Functional Tests.test/functional/apps/context/_size·js - context app context size should default to the context:defaultSize setting #53888

Closed
kibanamachine opened this issue Jan 2, 2020 · 11 comments · Fixed by #68213
Closed

Failing test: Chrome UI Functional Tests.test/functional/apps/context/_size·js - context app context size should default to the context:defaultSize setting #53888

kibanamachine opened this issue Jan 2, 2020 · 11 comments · Fixed by #68213
Assignees
@kertal
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test Feature:Discover Discover Application skipped-test Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Jan 2, 2020 •
edited
Loading

A test failed on a tracked branch

Error: retry.try timeout: Error: expected [ 'Sep 20, 2015 @ 12:34:59.79430.36.151.195 - - [2015-09-20T12:34:59.794Z] "GET /uploads/daniel-barry.png HTTP/1.1" 200 18202 "-" "Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.50 Safari/534.24"' ] to have a length of 15 but got 1
    at Assertion.assert (packages/kbn-expect/expect.js:100:11)
    at Assertion.length (packages/kbn-expect/expect.js:374:8)
    at /dev/shm/workspace/kibana/test/functional/apps/context/_size.js:45:54
    at process._tickCallback (internal/process/next_tick.js:68:7)
    at onFailure (test/common/services/retry/retry_for_success.ts:28:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:68:13)

First failure: Jenkins Build
@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Jan 2, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-test-triage (failed-test)

@spalger spalger added Feature:Discover Discover Application Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Feb 28, 2020
@spalger
Copy link
Contributor

spalger commented Feb 28, 2020

This has been happening a reasonable amount in PRs lately, but especially today... it's unclear why.

last 30 days:

image

today:

image

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app (Team:KibanaApp)

spalger added a commit that referenced this issue Feb 28, 2020
@spalger
skip flaky suite (#53888)
facae44
spalger added a commit that referenced this issue Feb 28, 2020
@spalger
skip flaky suite (#53888)
1b85349 
(cherry picked from commit facae44)
@spalger
Copy link
Contributor

spalger commented Feb 28, 2020 •
edited
Loading

Skipped

master: facae44
7.x/7.7: 1b85349
7.6: 54f8c49

@myasonik
Copy link
Contributor

myasonik commented Mar 12, 2020 •
edited
Loading

Just leaving a note that this blocking tests we wanted to introduce in #59375

CC @bhavyarm

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

1 similar comment
@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

spalger added a commit that referenced this issue Mar 19, 2020
@spalger
skip flaky suite (#53888)
54f8c49 
(cherry picked from commit facae44)
@spalger
Copy link
Contributor

spalger commented Mar 19, 2020

Skipped in 7.6 as well

@kertal kertal self-assigned this Mar 25, 2020
@kertal kertal mentioned this issue Jun 4, 2020
Merged
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kertal kertal

Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test Feature:Discover Discover Application skipped-test Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Discover] Unskip context size tests kertal/kibana
5 participants
@kertal @spalger @myasonik @elasticmachine @kibanamachine