-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Closed
Labels
:Core/Infra/CoreCore issues without another labelCore issues without another label>test-failureTriaged test failures from CITriaged test failures from CITeam:Core/InfraMeta label for core/infra teamMeta label for core/infra teamneeds:riskRequires assignment of a risk label (low, medium, blocker)Requires assignment of a risk label (low, medium, blocker)
Description
Build Scans:
- elasticsearch-intake #27194 / part1
- elasticsearch-pull-request #87090 / part-1
- elasticsearch-pull-request #87092 / part-1
- elasticsearch-pull-request #87086 / part-1
- elasticsearch-pull-request #87087 / part-1
- elasticsearch-pull-request #87052 / part-1-windows
- elasticsearch-pull-request #87076 / part-1
- elasticsearch-pull-request #87078 / part-1
- elasticsearch-pull-request #87054 / part-1
- elasticsearch-pull-request #87080 / part-1
Reproduction Line:
null
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
org.gradle.testkit.runner.UnexpectedBuildFailure: Unexpected build execution failure in /tmp/junit4589965804964154755 with arguments [:myserver:validateTransportVersionDefinitions, --full-stacktrace, -Dtest.external=true]
Output:
[Incubating] Problems report is available at: file:///tmp/junit4589965804964154755/build/reports/problems/problems-report.html
FAILURE: Build failed with an exception.
* What went wrong:
Cannot locate tasks that match ':myserver:validateTransportVersionDefinitions' as task 'validateTransportVersionDefinitions' not found in project ':myserver'.
* Try:
> Run gradle tasks to get a list of available tasks.
> For more on name expansion, please refer to https://docs.gradle.org/9.0.0/userguide/command_line_interface.html#sec:name_abbreviation in the Gradle documentation.
> Run with --info or --debug option to get more log output.
> Run with --scan to generate a Build Scan (Powered by Develocity).
> Get more help at https://help.gradle.org.
* Exception is:
org.g
[truncated]
Issue Reasons:
- [main] 5 consecutive failures in test named and unreferenced definitions cannot have the same name
- [main] 7 consecutive failures in step part1
- [main] 4 consecutive failures in step part-1
- [main] 7 consecutive failures in pipeline elasticsearch-intake
- [main] 4 consecutive failures in pipeline elasticsearch-pull-request
- [main] 28 failures in test named and unreferenced definitions cannot have the same name (93.3% fail rate in 30 executions)
- [main] 7 failures in step part1 (100.0% fail rate in 7 executions)
- [main] 20 failures in step part-1 (90.9% fail rate in 22 executions)
- [main] 7 failures in pipeline elasticsearch-intake (100.0% fail rate in 7 executions)
- [main] 18 failures in pipeline elasticsearch-pull-request (90.0% fail rate in 20 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Metadata
Metadata
Assignees
Labels
:Core/Infra/CoreCore issues without another labelCore issues without another label>test-failureTriaged test failures from CITriaged test failures from CITeam:Core/InfraMeta label for core/infra teamMeta label for core/infra teamneeds:riskRequires assignment of a risk label (low, medium, blocker)Requires assignment of a risk label (low, medium, blocker)