CASA Build and Test Group Meeting
Thursday, 7th May, 2015, 11:00; Room ER245.
Mark, Darrell, Ville, Andy, Akeem
Post-meeting edits and additions in blue text.
- Status of current CASA packages
- Release - 4.3.1 out for OS X (10.8) and RHEL 5 and 6
- 4.4 test/stable packages routinely being produced for RHEL5 and 6
- Pre-release packages being produced for RHEL 5, 6 and OS X 10.9 and 10.10. Any comments on remaining 4.4 blockers?
- Trunk commits to casacore are going through Jim right now...
- "Extended" tests being run on the tarball versions. Dirk's M100 test will routinely e-mail Mark and Andy in the future.
- Build and Test Review Status
- Casacore unification - Being worked on now. For reference, Jim's proposed plan was as follows:
- 0.5. Attempt to build against the GC casacore and identify problems. Done.
- 0.75. Iteratively fix bugs and attempt to build again. This was Shinnosuke's B&T primary assignment. Done.
- 1. Merge our Casacore into GC casacore. This will require us to flush all casacore mods in and then let Ger do the final merge (finally). Done.
- 2. Build CASA against GC casacore (platforms?) Done for Linux.
- 3. Test CASA/GC casacore against our various regression tests, etc. Done for Linux - can pass.
- 4. Create a Jenkins job that will handle B&T of codebase using GC casacore. Discussed at the previous meeting
- 5. Keep a cached, read-only copy of GC casacore locally(?) to prevent a glitch at googlecode/github from allowing us to build. Also we should maintain periodic a backup copies.
- 5.5. Survive the migration from GC to GitHub...
- 6. Go live and live happily ever after.
- B&T news/items from EA.
- B&T news/items from Charlottesville.
- Regression testing of OS X (10.10 and 10.9 test packages). ~6 tests currently failing (~1 on Linux). MPI test failing. Akeem was seeing the LDLIBRARY path sometimes being overwritten, rather than appended (in casaregression.py). Akeem will follow up with Darrell on this.
- Need a good clean write-up / script / whatever of how to build CASA on OS X and Linux (for developers). Some post-meeting suggestions made, including automatically producing a summary of the cmake commands used (with a full list of options selected) for each package build. For us to provide a full description of the build process, though, we would also need to document the environment used (which 3rd-party packages are installed, which versions, etc.). Also, B&T Group to try to help maintain Kumar's page. Status? Ville is currently documenting the details of the environment: the Mac side of things is largely done. In addition to the plan to print out the full cmake commands for all the nightly package builds, plans are afoot to also write out the associated environment details (paths, etc.). The level of detail on this can also perhaps be expanded upon in the future, as needed. Even if the developer build environment is a mess, at least it will hopefully soon be a documented mess, rather than an undocumented mess...
- We need to decide on a single place for instructions about building for developers, identify it to all the developers & get rid of the other, outdated documentation pages. Status? Ville has a wiki page he has been working on.
- Mark was asked at a previous HPC meeting to try to write down instructions for casa/casapy launch instructions for specific environments (for developers, multiple nodes, etc.) had received an initial e-mail from Julian about his understanding of the situation. No news, although Mark noted that the reported confusion had not been raised again, and so may actually have been functionally addressed during the original HPC meeting.
- Travis CI (and friends)? This was discussed. Potentially, it could replace the role of both Jenkins and the nightly test scripting. Due to the amount of associated work, any switch to this would be a longer-term solution. The "killer feature" offered is that it would enable us to perform OS X testing on a Linux server. It can be used to test code already posted to GitHub. If we do end up with out own NRAO GitLab set-up, we could try bolting Travis CI onto it and testing it on there for a small number of tests (it's one thing to use it as a GitHub end-user, but it might be more work to set up and administrate an NRAO installation of it). Not insignificant work would be required for this. Darrell and Ville were looking into OpenID as a possible authentication solution that would work within the NRAO IT security framework.
- Review short-term task priority lists Done during the meeting.
- Previous suggestion: We get a "floater" developer Mac Mini for Charlottesville. Probably most practical to set it up in Dave Mehringer's office? Some recent discussion. Dave has a older Mac. Maybe can be updated? It turns out that Dave has a Mac that hopefully just needs updating and setting up for developer use. Mark had opened an IT helpdesk ticket to ask Josh to update the machine to 10.10 (if possible), and then pass it to Ville (or Darrell) to set up the developer environment stuff.
- Old Action Items
- Andy: 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? (See above). It is noted that this AI is not a pressing issue at this point. Andy had started to have some discussion with Alexis about this. Smoke tests will be run on the new Test Group Macs. They still need to discuss test coverage for OS X and Linux. Ongoing, with the understanding that this is a lower priority item than Alexis' other work, and that his remaining contract period is limited.
- Next meeting: probably June, 2015.
- Any Other Business
- Mark will be away from the office for a few weeks
- Darrell will set up Ville with access to the administration account for the Geodetic data updates (he actually did this during the meeting).
New Action Items Arising