No labels!
There aren’t any labels for this repository quite yet.
An open issue or test failure that is a low risk to future releases
An open issue or test failure that is a medium risk to future releases
Requires assignment of a risk label (low, medium, blocker)
Requires assignment of a team area label
Added when a new aggregation is being introduced
Added when a new field type / mapper is being introduced
All issues related to Elasticsearch performance including regressions and investigations
A label for assessing bug priority to be used by ES engineers
A label for assessing bug priority to be used by ES engineers
A label for assessing bug priority to be used by ES engineers
failures that don’t fit into an existing label. Should have a comment proposing a new label
test failed due to randomization, and is reproducible given the seed
test failed due to uncontrolled randomness (thread scheduling, IO, other kernel inputs)
tests passed in PR but failed at merge due to semantic conflicts with code
the tests that failed weren’t run before merge, and would have failed if they had
tests fail due to reliance on events happening within some wall clock time
You can’t perform that action at this time.