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

[Discover] Unskip flaky histogram test #179974

Merged
merged 1 commit into from
Apr 5, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,7 @@ export default function ({ getService, getPageObjects }: FtrProviderContext) {
const log = getService('log');
const queryBar = getService('queryBar');

// FLAKY: https://github.com/elastic/kibana/issues/173904
describe.skip('discover histogram', function describeIndexTests() {
describe('discover histogram', function describeIndexTests() {
before(async () => {
await esArchiver.loadIfNeeded('test/functional/fixtures/es_archiver/logstash_functional');
await esArchiver.load('test/functional/fixtures/es_archiver/long_window_logstash');
Expand Down Expand Up @@ -75,7 +74,7 @@ export default function ({ getService, getPageObjects }: FtrProviderContext) {
const actualCount = await elasticChart.getVisualizationRenderingCount();
const expectedCount = prevRenderingCount + renderingCountInc;
log.debug(`renderings before brushing - actual: ${actualCount} expected: ${expectedCount}`);
return actualCount === expectedCount;
return actualCount <= expectedCount;
Copy link
Member

Choose a reason for hiding this comment

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

I have a question here the skipped test is failing because

actual: 2 expected: 1

With this change it will pass when the actual count is 0,1, ... but actually when there's an extra rendering, that we try to catch, it is not caught. My question, is the behavior als flaky when trying it out locally without any change?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi @kertal!

Currently it fails with renderings before brushing - actual: 3 expected: 4.

As @davismcphee mentioned in https://github.com/elastic/kibana/pull/178592/files we don't know why it can be 4 sometimes on serverless. Anything below 4, we can consider as a good result. Same is on line 93 https://github.com/elastic/kibana/pull/179974/files/a08221d61210bb78ffde8aa98e3d6a6a831636f3#diff-fa544caff5a4583101f0926db5dd31ce3c10983d491a97e4484126c709f715c6R93

Copy link
Member

Choose a reason for hiding this comment

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

thx @jughosta , LGTM , we could consider to skip such tests that need very specific serverless adaptation, when they are not critical like in this case

});
let prevRowData = '';
// to make sure the table is already rendered
Expand Down