Skip to end of metadata
Go to start of metadata

This is a DRAFT awaiting agreement from core team members. It was my view that having a single focused wiki page would assist in setting up and managing the stability drive.

The purpose of this page is to (ultimately) have:

  • an agreed set of goals for the stability drive,
  • a set of rules for commits during the stability drive,
  • a central list of the current failures that need to be resolved,
  • a central list of problems that have been identified from the failures, and
  • an assignment of these problems to core team members and volunteers.

Goals

The high level goal for the stability drive is (in priority order) to be able to:

  1. Reliably pass all nightly prototype sanity tests for DaCapo
  2. Reliably pass all nightly development sanity tests for DaCapo
  3. Reliably pass all nightly production sanity tests for DaCapo
  4. Reliably pass all nightly prototype sanity tests for SPEC (jvm98/jbb2000/jbb2005)
  5. Reliably pass all nightly development sanity tests for SPEC (jvm98/jbb2000/jbb2005)
  6. Reliably pass all nightly production sanity tests for SPEC (jvm98/jbb2000/jbb2005)

Commit Guidelines

TBD 

Persistent Failures

A) prototype eclipse EXCLUDED
B) prototype xalan OVERTIME: 480.08 sec

C) production eclipse EXCLUDED
D) production xalan unknown

Intermittent Failures 

E) prototype SPECjbb2000 OVERTIME: 1000.23 sec

F) production hsqldb unknown
G) production lusearch NullPointerException
H) production lusearch unknown
I) production SPECjbb2000 unknown
J) production SPECjbb2000 unknown
K) production SPECjbb2005 unknown
L) production SPECjbb2005 unknown

Issues

This section is yet to be filled. Issues identified from each of the cases above should be listed and associated tracker entry/entries should be referenced.

  • No labels