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: API Integration Tests.test/api_integration/apis/telemetry/opt_in·ts - apis Telemetry /api/telemetry/v2/optIn API "before all" hook for "should support sending false with allowChangingOptInStatus true" #144750

Closed
kibanamachine opened this issue Nov 7, 2022 · 4 comments
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@kibanamachine
Copy link
Contributor

A test failed on a tracked branch

Error: Forcing mocha to abort
    at Object.next (node_modules/@kbn/test/target_node/functional_test_runner/lib/mocha/run_tests.js:42:25)
    at SafeSubscriber.__tryOrUnsub (node_modules/rxjs/src/internal/Subscriber.ts:265:10)
    at SafeSubscriber.next (node_modules/rxjs/src/internal/Subscriber.ts:207:14)
    at Subscriber._next (node_modules/rxjs/src/internal/Subscriber.ts:139:22)
    at Subscriber.next (node_modules/rxjs/src/internal/Subscriber.ts:99:12)
    at RaceSubscriber.notifyNext (node_modules/rxjs/src/internal/observable/race.ts:137:22)
    at InnerSubscriber._next (node_modules/rxjs/src/internal/InnerSubscriber.ts:17:17)
    at InnerSubscriber.Subscriber.next (node_modules/rxjs/src/internal/Subscriber.ts:99:12)
    at TakeSubscriber._next (node_modules/rxjs/src/internal/operators/take.ts:92:24)
    at TakeSubscriber.Subscriber.next (node_modules/rxjs/src/internal/Subscriber.ts:99:12)
    at AbortSignal.handler (node_modules/rxjs/src/internal/observable/fromEvent.ts:201:20)
    at AbortSignal.[nodejs.internal.kHybridDispatch] (node:internal/event_target:694:20)
    at AbortSignal.dispatchEvent (node:internal/event_target:636:26)
    at abortSignal (node:internal/abort_controller:292:10)
    at AbortController.abort (node:internal/abort_controller:323:5)
    at onEarlyExit (node_modules/@kbn/test/target_node/functional_tests/tasks.js:112:21) {
  uncaught: true
}

First failure: CI Build - 7.17

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

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Nov 7, 2022
@afharo
Copy link
Member

afharo commented Nov 8, 2022

The error happened in the before step during the esArchiver.emptyKibanaIndex() request:

└-> "before all" hook for "should support sending false with allowChangingOptInStatus true"
             │ERROR [migrate saved objects] request failed (attempt=1/5): read ECONNRESET
             │ERROR [kibana] exitted early: [kibana] exited with code 1

Reassigning to @elastic/kibana-operations since they own esArchiver.

@afharo afharo added Team:Operations Team label for Operations Team and removed Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Nov 8, 2022
@spalger
Copy link
Contributor

spalger commented Nov 8, 2022

The issue is that core is still using esArchiver to manage the Kibana index. All of those instances need to be updated to kbnArchiver usage as described in #102552. There isn't currently a great replacement for esArchiver.emptyKibanaIndex() (issue) but we do have the APIs to clear saved objects of specific types, like kbnServer.savedObjects.clean() or you can use the "standard list" of saved objects types with kbnServer.savedObjects.cleanStandardList().

@afharo
Copy link
Member

afharo commented Aug 29, 2023

The API has changed (so have the tests), and it hasn't failed in a while. Closing.

@afharo afharo closed this as completed Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
failed-test A test failure on a tracked branch, potentially flaky-test Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

5 participants