| Version 1.9 Build 1556
|
|
Next: Check the Documentation
Up: Weekly Duties
Previous: Weekly Duties
There are two opportunities to declare a stable each week. The first occurs with Thursday daily
cumulative build, the second with Friday's weekly build. We check Thursday's build and if it there
are problems which might prevent a stable, we try and address them with the hope that the weekly
cumulative might be "stable".
These build constitute the stable candidates. The criteria for a stable are:
- 1.
- Must be a cumulative
- 2.
- All aips unit tests should pass. Tests may fail but the failure must be understood and
considered to be minor (i.e. similar to tDirectory failure on linux with NFS mounts).
- 3.
- assay().trytests() runs without failure.
- 4.
- dishlongtests() runs without failure.
- 5.
- no obvious failures in loading the help atoms
So what does this entail?
- 1.
- Examine build logs for glaring problems.
- 2.
- Look at the unit tests
- (a)
- linux_gnu
- (b)
- sun4sol_gnu
- (c)
- sun4sol_ntv
- 3.
- Run assay
- (a)
- linux_gnu
- (b)
- sun4sol_gnu
- (c)
- sun4sol_ntv
If the build is "stable", then as aips2adm on tarzan
- 1.
- Send an email to aips2-naug aips2-aoc warning of the impending build
Greetings,
Build xx.yyy has met the stable criteria. We will begin building the new stable @hhmm MT.
Please use weekly until the new stable build has completed.
aips2mgr
- 2.
- as aips2adm;
cd /export/aips++/scripts; sh ./do\_blessing xx.yyy
This scripts marks xx.yyy as stable; inhales the stable into /aips++/stable; and begins the stable
build for linux and solaris. The local sgi stable build is triggered by it's own cron job.
- 3.
- Once the stable build completes, as aips2mgr on tarzan;
cd; cd scripts; ./updatestables.sh
This will update the stable builds area on /home/tarzan5 making binaries available to users via
aupdate.
- 4.
- Send an email to aips2-sitemgr
Greetings,
Build xx.yyy has been declared stable. Please update your stable releases.
aips2mgr
It's best to declared a stable no later than Monday afternoon, so remote sites can
inhale the latest stable Monday evening.
Next: Check the Documentation
Up: Weekly Duties
Previous: Weekly Duties
  Contents
  Index
Please send questions or comments about AIPS++ to aips2-request@nrao.edu.
Copyright © 1995-2000 Associated Universities Inc.,
Washington, D.C.
Return to AIPS++ Home Page
2006-10-15