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

Failing test: Jest Integration Tests.src/core/server/saved_objects/migrationsv2/integration_tests - migration v2 rewrites id deterministically for SO with namespaceType: "multiple" and "multiple-isolated" #98351

Closed
kibanamachine opened this issue Apr 26, 2021 · 5 comments · Fixed by #98478 or #101813
Assignees
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0

Comments

@kibanamachine
Copy link
Contributor

kibanamachine commented Apr 26, 2021

A test failed on a tracked branch

Error: write after endError [ERR_STREAM_WRITE_AFTER_END]: write after end
    at WriteStream.write (internal/streams/writable.js:292:11)
    at FileAppender.append (/dev/shm/workspace/parallel/5/kibana/src/core/server/logging/appenders/file/file_appender.ts:56:23)
    at BaseLogger.log (/dev/shm/workspace/parallel/5/kibana/src/core/server/logging/logger.ts:54:16)
    at BaseLogger.info (/dev/shm/workspace/parallel/5/kibana/src/core/server/logging/logger.ts:33:10)
    at LoggerAdapter.info (/dev/shm/workspace/parallel/5/kibana/src/core/server/logging/logger_adapter.ts:36:17)
    at HttpServer.start (/dev/shm/workspace/parallel/5/kibana/src/core/server/http/http_server.ts:203:14)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at HttpService.runNotReadyServer (/dev/shm/workspace/parallel/5/kibana/src/core/server/http/http_service.ts:240:5)
    at HttpService.setupNotReadyService (/dev/shm/workspace/parallel/5/kibana/src/core/server/http/http_service.ts:192:27)
    at HttpService.setup (/dev/shm/workspace/parallel/5/kibana/src/core/server/http/http_service.ts:91:28)
    at Server.setup (/dev/shm/workspace/parallel/5/kibana/src/core/server/server.ts:137:23)
    at Root.setup (/dev/shm/workspace/parallel/5/kibana/src/core/server/root/index.ts:42:14)
    at Object.<anonymous> (/dev/shm/workspace/parallel/5/kibana/src/core/server/saved_objects/migrationsv2/integration_tests/rewriting_id.test.ts:143:23)

First failure: Jenkins Build

@kibanamachine kibanamachine added the failed-test A test failure on a tracked branch, potentially flaky-test label Apr 26, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 26, 2021
@mistic mistic added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Apr 26, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 26, 2021
mistic added a commit that referenced this issue Apr 26, 2021
mistic added a commit that referenced this issue Apr 26, 2021
@mistic
Copy link
Member

mistic commented Apr 26, 2021

This test was failing on CI and I've skipped it to unblock it.

master/8.0: 56bce08
7.x/7.14: c104ad2

@spalger
Copy link
Contributor

spalger commented May 19, 2021

This suite just failed in master because the es version loading the data archive is using a trial license which has now expired. I think we should probably disable the use of trial licenses when supplying a dataArchive in esArchiver, but we might need to be able to overwrite that in specific cases where the data archive was created using a basic license or something...

Skipped:

master: c0d81c9
7.x/7.14: @mshustov looks like the 7.x backport of #98478 didn't unskip this suite, just the "cleanup" suite, was that intentional? Should we remove these tests?

@spalger spalger reopened this May 19, 2021
@mshustov
Copy link
Contributor

mshustov commented May 19, 2021

was that intentional? Should we remove these tests?

yes and yes. I will take care of it

@kibanamachine
Copy link
Contributor Author

New failure: Jenkins Build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker failed-test A test failure on a tracked branch, potentially flaky-test skipped-test Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc v8.0.0
Projects
None yet
5 participants