Slight modification to this -- I'd still like to distinguish between getting a *bad* checksum back from not finding the app. Bad checksums should still Abort (actually, perhaps it would be better if they gracefully fail -- not abort!), whereas not finding the app should be a Debug.
The md5sum() and sha1sum() functions should return undef if they can't find the app. > -----Original Message----- > From: mtt-users-boun...@open-mpi.org > [mailto:mtt-users-boun...@open-mpi.org] On Behalf Of Ethan Mallove > Sent: Monday, July 10, 2006 3:56 PM > To: General user list for the MPI Testing Tool > Subject: [MTT users] sha1sum on x64 Solaris > > I'm not sure sha1sum is installed by default on x64 Solaris > systems. I don't see it on any of our > x64 Solaris lab machines. (Not sure how this wasn't a problem > until now.) Until we figure out how to > do SHA1 checksums on x64 Solaris, my workaround is to simply > change Abort to Debug when the sha1sum > checksum comparison fails: > > > Index: lib/MTT/MPI/Get/OMPI_Snapshot.pm > =================================================================== > --- lib/MTT/MPI/Get/OMPI_Snapshot.pm (revision 191) > +++ lib/MTT/MPI/Get/OMPI_Snapshot.pm (working copy) > @@ -128,7 +128,7 @@ > my $sha1_file = `grep $ret->{version}.tar.gz > $sha1_checksums | cut -d\\ -f1`; > chomp($sha1_file); > my $sha1_actual = > MTT::Files::sha1sum("$tarball_dir/$tarball_name"); > - Abort("sha1sum from checksum file does not match actual > ($sha1_file != $sha1_actual)") > + Debug("sha1sum from checksum file does not match actual > ($sha1_file != $sha1_actual)") > if ($sha1_file ne $sha1_actual); > Debug(">> Good sha1sum\n"); > > > -Ethan > > _______________________________________________ > mtt-users mailing list > mtt-us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users >
