Reporting Bugs

Thanks for your interest in HSA.  One of the best ways you can help us improve HSA Tools and Runtimes is to let us know about any problems you find with it.

To report General bugs:

First search to see if  your bug has already reported it.

If you find your issue and it’s important to you, add a comment to this bug reporting more information That’s how we know which bugs are most important to fix.

If no one has reported the bug, file a bug report. You can use one of these templates:

  • Bug in Compiler – use this if you are a user reporting a bug in the llvm based compiler
  • Bug in libHSA- use this if you found a bug in the course of developing an application, library or tools with libHSA
  • Bug in HSA Runtime use this if you found a bug in the course of developing an application, library or tools with the HSA Runtime
  • Feature Request – use this for a feature you’d like to see in a future version

Please put as much information in bug reports as you can so the team can evaluate the issue properly

To report security vulnerability

First, though: if you think you’ve found a security vulnerability, please report the issue too HSA security team <security  @ hsafoundation.com>.

The HSA Foundation Community Source Project maintains a public issue tracker where you can report bugs and request features for the HSA Foundation software projects.

 

The life of a bug:

A bug is filed, and has the state “New”.

An HSAF_CSP  contributor periodically reviews and triages bugs. Bugs are triaged into one of four “buckets”: New, Open, No-Action, or Resolved.

Each bucket includes a number of states that provide more detail on the fate of the issue.

Bugs in the “Resolved” state will eventually be included in a future release of the Android software.

 

Bug states details

Here is some additional information on each state, what it means, and how it’s handled.

New Issues: New issues include bug reports that are not yet being acted upon. The two states are:

  • New: The bug report has not yet been triaged (that is, reviewed by an HSAF_CSP  contributor.)
  • NeedsInfo: The bug report has insufficient information to act upon. The person who reported the bug needs to provide additional detail before it can be triaged. If enough time passes and no new information is provided, the bug may be closed by default, as one of the No-Action states.

Upon review they move to one of the following states,

  • Open Issues: This bucket contains bugs that need action, but which are still unresolved, pending a change to the source code.
  • Unassigned: The bug report has been recognized as an adequately detailed report of a legitimate issue, but has not yet been assigned to an HSAF_CSP contributor to be fixed. Typically, bugs in this state are considered low priority, at least insofar that if they were high priority, they’d be assigned to a contributor.
  • Reviewed: Like Unassigned, but the issue represented is being tracked in a separate bug database. For example, the bug might have been reported via an internal bug-tracking system, which is considered the “master” copy. (For instance, HSA Foundation maintains one such private issue tracker, intended primarily for bugs which contain sensitive information which can’t be revealed publicly.)
  • Assigned: Like Unassigned, but the bug has been actually assigned to a specific contributor to fix.
  • No-Action Issues: This bucket contains bugs that have for one reason or another been determined to not require any action.
  • Spam: will be culled from the bugs database.
  • Unreproducible: An HSAF_CSP  contributor attempted to reproduce the behavior described, and was unable to do so. This sometimes means that the bug is legitimate but simply rare or difficult to reproduce, and sometimes means that the bug was fixed in a later release.
  • WorkingAsIntended: An HSAF_CSP  contributor has determined that the behavior described isn’t a bug, but is the intended behavior. This state is also commonly referred to as “WAI”.
  • Declined: This is like WorkingAsIntended, except typically used for feature requests instead of bugs. That is, an HSAF_CSP  contributor has determined that the request is not going to be implemented in HSA Software Project.
  • Resolved Issues: This bucket contains bugs that have had action taken, and are now considered resolved.
  • Future-Release: This bug has been fixed (or feature implemented) in a source tree, but has not yet been included in a formal HSA software project release. (Note that this may also include fixes that exist in a private source tree that has not yet been contributed to a public tree.)
  • Released: This bug has been fixed, and is included in a formal HSA software project release. When this state is set, we try to also set a property indicating which release it was fixed in.
  • Duplicate: This bug is a duplicate of another, existing bug report.