Filing bugs for HotSpot failures

If a new failure is found a bug should be filed in JBS. Try to make the bugs as complete as possible to make it easier to triage and investigate the bug. It's not really the reporter's responsibility to set a correct priority, but a good guess is always better than a default value. To help with setting the right priority consider things like how the bug impacts the product and our testing, how likely is it that the bug triggers, and how difficult is it to work around the bug if it is not fixed soon. To find out which component to use for different bugs look at Hotspot JBS components. Once a bug has been filed component triage should verify that labels, priority, affected version, and descriptions are correct and set the fix version.

A few things to keep in mind when filing a new bug

Before filing a bug, verify that there isn't already a bug filed for this issue.
Any bug that is blocking integration should be labeled 'integration_blocker'.
- Any bug that is present in the tested repository and is not already present upstream is blocking integration. Basically all new failures are integration blockers and should be labeled as such. For more information see Integration and Integration Blockers.
Add other relevant labels like 'intermittent', 'regression', 'testbug'... etc.
Set affects version.
In the description, always include (if present):
- full name of the failing test(s)
- error messages
- assert messages
- stack trace
- command line information
- relevant information from the logs
Always file separate bugs for different issues.
- If two crashes looks related but not similar enough to for sure be the same, it is easier to close a bug as a duplicate than it is to extract the relevant info from a bug to create a new one later.

All new failures are considered integration blockers

If a failure is determined to be due to a broken test and the test is not expected to be fixed before the next nightly, it is OK to quarantine the test to be able to get a "clean" nightly. The JBS issue used to quarantine the test should be a sub-task to the original bug and the integration_blocker label is moved to the sub-task. This way, when the test has been quarantined, the bug is no longer a blocker.