CASA Build and Test Group Meeting
Tuesday, 21st October, 2014, 18:00; Room ER331.
Wednesday, 22nd October, 2014, 07:00.
DIAL-IN NUMBERS & PASSCODES:
USA Toll Free Number:
USA Toll Number:
In practice, these telecons are usually conducted via Google+ Hangouts/Voice).
Mark Rawlings, Darrell Schiebel, Shinnosuke Kawakami, Andy Hale
Post-meeting edits and additions are in blue text.
- Status of current CASA packages
- Redefinition of "test" and "stable" currently being implemented (see also below).
- Release - 4.2.2 out for OS X (10.8) and RHEL 5 and 6. 4.2.2 release has been successfully installed in Japan.
- Still receiving applications for B&T engineer. Currently in a "holding pattern": discussion of hiring a consultant short-term has rather stalled...
- Interviewing ongoing for Testing Automation position (Andy Hale's group). Mark and Darrell are on the hiring committee for this position as well. One on-site interview last week. Perhaps one or two more phone interviewing this/next week. Close to completion?
- Build and Test Review Status
- No news. Review timeline effectively on hold, pending above decisions regarding B&T hiring strategy.
- Casacore unification - Being worked on now. For reference, Jim's proposed plan was as follows:
- 0.5. Attempt to build against the GC casacorem and identify problems. DONE. Shinnosuke has effectively completed this task.
- 0.75. Iteratively fix bugs and attempt to build again. This is Shinnosuke's B&T primary assignment for the short-term. Ongoing. Ger has been working with Shinnosuke on this.
- 1. Merge our Casacore into GC casacore. This will require us to flush all casacore mods in and then let Ger to the final merge (finally).
- 2. Build CASA against GC casacore (platforms?)
- 3. Test CASA/GC casacore against our various regression tests, etc.
- 4. Create a Jenkins job that will handle B+T of codebase using GC casacore.
- 5. Keep a cached, readonly copy of GC casacore locally(?) to prevent a glitch at googlecode from allowing us to build. Also we should maintain periodic a backup copies.
- 6. Go live and live happily ever after.
- B&T news from Charlottesville.
- Most of the new package production system is now in place. Already pushed out to CASA developers nodes in Socorro. Holding back on data reduction cluster deployment in CV, pending wrapper script handling of additional tarball installation reporting. Already seeing benefits in terms of turnaround of science user testing. Test packages build runs are being triggered daily. Most user testers now seem to be happy enough with the new system.
- Mark has written up the current and planned structures available so far, including version numbering. Iterated on documentation with Socorro (Rob) and EA (Kana). Still to write up: the process "behind the scenes"...
- The 4.3 release branch has been produced. Developers should check in subsequent 4.3 bug fixes to both trunk and release. A pre-release package is imminent. (Post-meeting note: This was made available to user testers on the designated testing machines the following afternoon.
- Updates to the launcher wrapper are available this week, supporting launch of the pre-release packages. Post-meeting note: this happened the following afternoon, and user testers now have access to the pre-release package for 4.3 bug fix testing, including an OS X 10.8 package.
- Next job: Have the launcher script see (and report back the existence of) tarball installations as well.
- B&T news from EA.
- Many of the CASA 4.3 Single Dish jobs that had been done have been merged into the release branch now.
- Shinnosuke has been working on the casacore unification issue (also see above). The work for this is tracked on Jira ticket https://bugs.nrao.edu/browse/CAS-6929. Ger has been communicating with Shinnosuke on this. Shinnosuke estimates that 70% of the casacore code has been merged with Google Code. He hopes to complete this step within the next week or two.
- Shinnosuke has fixed the recently-discovered asynch bug.
- Old Action Items
- Mark to send Bunyo the URLs for the new-style tarballs (they can choose whether they prefer to use the RHEL5 or RHEL6 builds). Mark sent Bunyo the wiki page URLs containing his descriptions of the new packaging scheme.
- Darrell to provide help to Shinnosuke on creating a development branch to capture code changes that he implements for the casacore reunification effort.Generally agreed to be moot at this point, and so will be dropped.
- Next meeting: November 4th, 2014
- Any Other Business
- Darrell: Jenkins tests for check-ins for OS X. We may also want to get Alexis in on the discussions of this.
New Action Items Arising
- Action Item on Andy Hale: Discuss Jenkins test for check-ins on OS X with Alexis: same (or different?) smoke tests for OS X as for Linux? Related: machines in Socorro for this? (It was noted during the meeting that this AI is not a pressing issue at this point).