Release coordination

From Einstein Toolkit Documentation
Revision as of 09:44, 30 May 2016 by Eschnett (talk | contribs) (BAD: (something went critically wrong))
Jump to: navigation, search

Release Coordination

There are several places where we coordinate about this release:

  • Release_Process
  • Release_Details
  • Release_coordination (this page)
  • TRAC ticket

Make sure you check all places for information.

Once a specific issue has been identified, please create a ticket and move discussion there, and add the release milestone to the ticket. This page is just for coordination of "the test failures".

Put Stuff Here

Please list here, with your name, the machines which you care about.

Activity

Please describe what you are working on to avoid duplication of effort.

Testing on various machines

Erik Schnetter is running the tests on various machines. The current status is:

NEEDS-RUNNING:

Machines I plan to test, but I haven't done anything about them yet.

  • stampede-mic
  • titan

RUNNING:

  • mp2
  • sunnyvale

NEEDS-ANALYSIS

This means that the runs completed, but I did not look at the results yet.

  • bluewaters
  • orca
  • philip
  • qb
  • smic

GOOD

This means that test results are available on https://build.barrywardell.net/view/EinsteinToolkitMulti/job/EinsteinToolkitReport-sandbox .

  • bethe
  • comet
  • cori
  • gordon
  • gpc
  • nvidia
  • redshift
  • zwicky

BAD

Something went critically wrong. I might have some comments with a preliminary analysis.

  • datura: not accessible (2016-05-30)
  • edison: password expired (2016-05-30)
  • guillimin: build failure (2016-05-30)
  • mike: no access (2016-05-30)
  • shelob: cannot log in (2016-05-27); probably no LSU allocation; need to contact frank
  • stampede: allocation problems (2016-05-27); xsede portal has allocation; wait and retry