Search


DASWG LAL Doxygen

Docs

How-To's
Technical
Software Docs
Minutes

Download

Browse CVS, Git, or SVN
Software Repositories
OS Security Updates
LIGO software virtual machine
VMware SL6 Install

Participate

SCCB - Software Change Control Board
Edit these pages
Sub-committees
Mailing List
Telecon

Projects

DMT
DQSEGDB
Glue
GraceDB
gstlal
LALSuite
LDAS Tools
LDG Client/Server
LDR
ligoDV
LIGOtools
LVAlert Administration
LVAlert
MatApps
Metaio
NDS Client
PyLAL
LSCSOFT VM

Legacy Projects

geopp
LDAS
LDM
LIGOtools
LSCGIS
Onasys
OSG-LIGO

LAL/LALApps Bug Report Entry Page for Gnats

LAL and LALApps use the gnatsweb interface to the gnats probelem tracking database. The instructions on this page should help you get started. For more information see the Gnatsweb User Guide.

Instruction for anonymous users of gnats

Anonymous access will allow you to surf the bug reports and file bug reports, but you will not be able to edit or close bug reports.

  1. When you have read these instructions, follow the link at the bottom of this page to enter the gnats database.
  2. To log into gnats at the Login prompt, enter the anonymous username and password.
    • The anonymous user name is anonymous
    • The anonymous password is anonymous
    Note that GNATS will let you in even if you misspell the user name or password.
  3. To surf all the existing open bug reports push the "query" button. Then on the next page push the "submit query" button without changing any values in the pop-up menus.
  4. To file a bug report use the "create" button. Be sure to give your email address and choose the most appropriate category. See below for instructions on categorizing errors. Be sure to choose the correct Submitter-ID ("anonymous" if you logged in as anonymous). Please put your name in the Originator field.

Instructions for developers using gnats

  1. When you have read these instructions, follow the link at the bottom of this page to enter the gnats database.
  2. Note: Gnats uses virulent cookies. If you have entered gnats before, it will let you in without entering a user name or password, even if the username and password were incorrect. Check the User: and Access: fields at the top of the page after you log in. If your Access is not edit then click LOG OUT and try and log in again.
  3. To get a gnats account you can request an account or password update with our online form. If you've already used this form to gain VCS (version control system) access, you can likely log into Gnats with the same credentials. Finally, you can use this form to update your password.
  4. To log into gnats at the Login prompt, enter your username and password. If you are a LAL developer and need a user name and password for Gnats, send an email to the LAL librarian.
    Note: If you enter your user name or password incorrectly, gnats still lets you in with no warning. If your Access in the page header displays viewconf click LOG OUT and try and log in again.
  5. To surf the existing open bug reports push the "query" button. Then on the next page push the "submit query" button without changing any of the options in the pop-up menus. You can (and should) surf the options available, such as querying by individual, but this will get you started.
  6. To file a bug report use the "create" button. Be sure to give your email address and choose the most appropriate category. See below for instructions on categorizing errors. Be sure to choose the correct Submitter-ID ("anonymous" if you logged in as anonymous). Please put your name in the Originator field.
  7. To close a bug report use the "edit" button. Change the "state" from open to closed. Be sure to give a reason for the change.

The "severity" and "priority" of bugs

Obviously, some judgement is called for when deciding how to catagorize a bug your are filing. A reasonable set of guidelines can be found in the Gnats Vesion 3 Manual

Categories of errors.
severity: critical, serious, non-critical
priority: high, medium, low

Some common examples:
  1. If the bug causes the LAL build to fail, thus keeping people from being able to work, it is a critical bug with high priority.
    These types of bugs should be fixed on a timescale of minutes. Run the test script before -- and after -- committing your code to the CVS!
  2. If code runs but gives incorrect answers: severity is critical, priority is medium
  3. Documentation in a package is unclear: severity is serious, priority is medium

LAL/LALApps Bug Report System

Log into LAL/LALApps Bug Reporting System

$Id$