Labels
Labels
736 labels
- An open issue or test failure that is a low risk to future releases
- Tracking issue that arise during the development of Lucene 10.3
- An open issue or test failure that is a medium risk to future releases
- Java Modules related
- Requires assignment of a risk label (low, medium, blocker)
- Requires assignment of a team area label
- 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
- Added by automation, don't add manually
- Marking issues only relevant for stateful releases
- Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better.