Criteria for Automated Reporting Exceptions to Bugzilla


Before the exception report can be transfered to the bugzilla bug tracking system, it has to meet certain criteria. First thing done after the exception report arrives is duplicate analysis. Then the exception must pass at least one of the filters, which are described below. Reports reported by GUEST users are not propagated into bugzilla directly at all.

Filter definition

(At least one of the following statements has to be true)

  • Exception report has 5 duplicates
  • Exception type is NullPointerException, AssertionError, IllegalArgumentException or MissingResourceException
  • Reporter is netbeans QE member (usernames are listed here)

Raise Bug Priority

  • P2 if the bug has 20 duplicates
  • P1 if the bug has 50 duplicates

Reopen as a new Bug

Bugs are reopen no more, because while there are incorrect duplicates it's hard to split them and some bugs are being reopen again and again. New bug is created instead, reports at statistics are splitted accordingly and link to the old bug is added.

(All the statements have to be true)

  • Resolution is not INVALID, WONTFIX or DUPLICATE
  • Reporter is not a GUEST

In case user is using a daily build and the bug fix was already migrated into main-golden repository:

  • (User's IDE build number) >= (first daily build with the fix)

In case user is not using a daily build or the bug fix was not yet migrated into main-golden repository:

  • (build date) > (bug fix date + 10 days)
  • TM of reported exception is the same or newer than TM of the fix
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo