-
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
Failing test: Entity Analytics - Risk Engine Integration Tests - Serverless Env - Complete Tier.x-pack/test/security_solution_api_integration/test_suites/entity_analytics/risk_engine/trial_license_complete_tier/init_and_status_apis·ts - Entity Analytics - Risk Engine @ess @serverless @serverlessQA init_and_status_apis status api should return status of legacy risk engine #196166
Labels
blocker
failed-test
A test failure on a tracked branch, potentially flaky-test
skipped-test
Team:Entity Analytics
Security Entity Analytics Team
v9.0.0
Comments
kibanamachine
added
the
failed-test
A test failure on a tracked branch, potentially flaky-test
label
Oct 14, 2024
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this issue
Oct 15, 2024
…le test (elastic#196172) ## Summary Closes elastic#196166 The test is checking that when we disable the risk engine, the risk ewngine task is registered but not actively running. This check originally checked if the task status was "idle". We have had a failure where the task status is "claiming", reading the docs about this task status (below) this is also an acceptable "non-running" status ``` // idle: Task Instance isn't being worked on // claiming: A Kibana instance has claimed ownership but hasn't started running // the Task Instance yet ``` (cherry picked from commit 40bfd12)
New failure: kibana-on-merge - main |
kibanamachine
added a commit
that referenced
this issue
Oct 16, 2024
… in disable/enable test (#196172) (#196454) # Backport This will backport the following commits from `main` to `8.x`: - [[Entity Analytics] Allow task status to be "claiming" in disable/enable test (#196172)](#196172) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Mark Hopkin","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-10-15T22:27:50Z","message":"[Entity Analytics] Allow task status to be \"claiming\" in disable/enable test (#196172)\n\n## Summary\r\n\r\nCloses #196166 \r\n\r\nThe test is checking that when we disable the risk engine, the risk\r\newngine task is registered but not actively running.\r\n\r\nThis check originally checked if the task status was \"idle\".\r\n\r\nWe have had a failure where the task status is \"claiming\", reading the\r\ndocs about this task status (below) this is also an acceptable\r\n\"non-running\" status\r\n\r\n```\r\n // idle: Task Instance isn't being worked on\r\n // claiming: A Kibana instance has claimed ownership but hasn't started running\r\n // the Task Instance yet\r\n```","sha":"40bfd12cc55ebfb1641ef21133fb009c23b0106f","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-minor","Team:Entity Analytics"],"title":"[Entity Analytics] Allow task status to be \"claiming\" in disable/enable test","number":196172,"url":"https://github.com/elastic/kibana/pull/196172","mergeCommit":{"message":"[Entity Analytics] Allow task status to be \"claiming\" in disable/enable test (#196172)\n\n## Summary\r\n\r\nCloses #196166 \r\n\r\nThe test is checking that when we disable the risk engine, the risk\r\newngine task is registered but not actively running.\r\n\r\nThis check originally checked if the task status was \"idle\".\r\n\r\nWe have had a failure where the task status is \"claiming\", reading the\r\ndocs about this task status (below) this is also an acceptable\r\n\"non-running\" status\r\n\r\n```\r\n // idle: Task Instance isn't being worked on\r\n // claiming: A Kibana instance has claimed ownership but hasn't started running\r\n // the Task Instance yet\r\n```","sha":"40bfd12cc55ebfb1641ef21133fb009c23b0106f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/196172","number":196172,"mergeCommit":{"message":"[Entity Analytics] Allow task status to be \"claiming\" in disable/enable test (#196172)\n\n## Summary\r\n\r\nCloses #196166 \r\n\r\nThe test is checking that when we disable the risk engine, the risk\r\newngine task is registered but not actively running.\r\n\r\nThis check originally checked if the task status was \"idle\".\r\n\r\nWe have had a failure where the task status is \"claiming\", reading the\r\ndocs about this task status (below) this is also an acceptable\r\n\"non-running\" status\r\n\r\n```\r\n // idle: Task Instance isn't being worked on\r\n // claiming: A Kibana instance has claimed ownership but hasn't started running\r\n // the Task Instance yet\r\n```","sha":"40bfd12cc55ebfb1641ef21133fb009c23b0106f"}}]}] BACKPORT--> Co-authored-by: Mark Hopkin <[email protected]>
New failure: kibana-on-merge - main |
Skipped. main: f1e4d8f |
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:Entity Analytics
Security Entity Analytics Team
v9.0.0
A test failed on a tracked branch
First failure: kibana-on-merge - main
The text was updated successfully, but these errors were encountered: