1 / 12

NRI (Night Reporting Infrastructure) for VLT Common Software Integration

NRI (Night Reporting Infrastructure) for VLT Common Software Integration. S. Feyrin, M. Zamparelli European Southern Observatory. Contents. NRI Generalities : NRI/dynamic: motivation and requirements NRI Layout NRI for vltsw Possible changes and extensions. NRI/dynamic: motivation.

guinevere-mckinney
Download Presentation

NRI (Night Reporting Infrastructure) for VLT Common Software Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. NRI(Night Reporting Infrastructure)for VLT Common SoftwareIntegration S. Feyrin, M. Zamparelli European Southern Observatory

  2. Contents • NRI Generalities : • NRI/dynamic: motivation and requirements • NRI Layout • NRI for vltsw • Possible changes and extensions NRI for VLTSW

  3. NRI/dynamic: motivation • shorten the feedback loops from manual integration • bring to the attention of the developers software modules with missing or insufficient testing • bring to the attention of the developers software modules with suspect memory fingerprint • diminish the labor pain when migrating to new compiler version or OS release • have minimal trend analysis for various performance indicators NRI for VLTSW

  4. Requirements on NRI • Build environment should be the correct one • All applicable platforms should be exercised • Static and dynamic reports should correspond to the same version of the software • The build should take place from scratch • Tests should be executed in isolation (FIFO) • Ease of access to reports on the web for diagnosis • Tests running amock should not halt the integration NRI for VLTSW

  5. Configuration Management source Codewizard JTest sloccount cmt/cmtjava JDepend doxygen graphviz Purify/Valgrind splint JContract reports NRI Layout Database WebServer Static Inspection (dynamic inspection machines) host1 host2 host3 NRI for VLTSW

  6. Machines NRI for VLTSW

  7. Integration Steps 1: normal build 2: normal test (TAT or otherwise based) 2,5: additional purify and test (if applicable) 3: purified build (vltMakefile based) 4: purified test (TAT or otherwise based) NRI for VLTSW

  8. NRI for VLTSW • Dynamic (build and test) Adapt NRI to work with non Makefile based approach of VLTSW Align results of automated integration and tests with the manual ones Solve problems related on LCU availability and usage Solve display related problems • Dynamic (coverage and memory reports) Run through PureCoverage and get consistent results!! Improve layout and readability of coverage reports Separate the weed from the crop in memory reports • Notification (responsibility assignment) • Static part NRI for VLTSW

  9. Links to the Web • http://websqa.hq.eso.org/vlt/snapshot2/ • http://websqa.hq.eso.org/vlt/snapshot3/vltsw-Reports/TestCoverage-Linux / NRI for VLTSW

  10. Test result determination Purify Compiled Test DIR Makefile TAT signature UNDETERMINED test target UNDETERMINED TAT Purify make test test output FAILED PASSED NRI for VLTSW

  11. Problems and Solutions (?) • Execution time on HP-UX is prohibitive • LAST or non LAST ? • How frequently should it run ? • Tools license availability ? • pkingBuild should build a partition of the CMM modules space (http://websqa.hq.eso.org/vlt/PackagesAnalysis.html ) NRI for VLTSW

  12. NRI: dynamic + static Implementation of Integration steps on a “daily” basis • Daily build report on appropriate OS from last code revision • Coding Standards (actually industry best practices) reports (VLTSW20030379 VLTSW20030380) • Naming conventions, dependency diagrams, subsystem partition in modules. • McCabe Cyclomatic Complexity and Halstead Volume, in-line documentation sufficency • in-line documentation • Lines of code at subsystem and global level • test lines of code at subsystem level • Unit test coverage • amount of check-in operations • SPRs per subsystem NRI for VLTSW

More Related