Hi Alan,
Oh, I should have checked all this more carefully. Hm, right now there is an
update running for Cygwin and this is taking a remarkably long time. I will
prepare the new test run by cleaning up the directory. As I thought the script
had done that, I copied the subdirectories that were touched into the tarball.
Hopefully I will get a chance to rerun the test before I have to leave for home
;).
Regards,
Arjen
> -----Original Message-----
> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> Sent: Friday, April 17, 2015 2:44 PM
> To: Arjen Markus
> Cc: PLplot development list
> Subject: RE: Comprehensive testing: Cygwin
>
> On 2015-04-17 10:05-0000 Arjen Markus wrote:
>
> >> -----Original Message-----
> >> From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca]
> >>
> >> Hi Arjen:
> >>
> [....]
>
> > Please have a look at the tarball - I have included all the information you
> > asked for.
>
> I cannot find everything I requested in the tarball. So I repeat what I
> asked for before
> in numbered form.
>
> 1. Output from the printenv command (which gives a list of all environment
> variables);
>
> 2. the script you used to invoke scripts/comprehensive_test.sh
>
> 3. complete scripts/comprehensive_test.sh output;
>
> 4. and all the files in the relevant output_tree subdirectories.
>
> I believe you sent me 1. as env.out in the tarball, but I can find no sign of
> 2. or 3. in
> the tarball.
>
> You did send me 4, but I believe there are stale files left in there from
> previous runs
> of the script (although I am not sure because I don't have 3).
>
> You also sent me the unrequested build_dir in the tarball. I didn't request
> that part of
> the generated results because those large files are fairly useless to me. So
> please
> drop that the next time to save bandwidth, i.e., only include results from
> the relevant
> output_tree subdirectories for 4.
>
> 5. However, those build_dir results did give me an idea which is it would be
> useful to
> have a detailed listing of all files that were generated by the test. Of
> course, that
> listing is fairly large (mine here contains 30 thousand files in the listing!)
>
> To generate such a list do the following:
>
> cd $prefix #where $prefix is the prefix containing all the results
>
> find . -type f |xargs ls -l >& listing.out
>
> and include that listing.out in the tarball.
>
> What I suggest you do to make the requested data collection completely
> repeatable
> and automatic is make those commands part of your bash script that invokes
> scripts/comprehensive_test.sh.
>
> So what that overall script should do is the following.
>
> A. Remove all the stale results from previous runs of the script.
>
> B. Capture printenv output
>
> C. Run scripts/comprehensive_test.sh with output captured using the tee
> command
> as discussed previously here when discussing the same subject with Greg, i.e.,
>
> scripts/comprehensive_test.sh |& tee comprehensive_test.sh.out
>
> D. Add further commands to collect all the requested additional information
> and pack
> it in a tarball.
>
> B and C take care of requests 1 and 3 above so D must handle request 2, 4,
> and 5.
>
> If you need bash scripting help with any of A through D, let me know.
>
> Thanks in advance for this additional effort to automate the data collection
> for your
> comprehensive tests.
>
> Alan
>
> __________________________
> Alan W. Irwin
>
> Astronomical research affiliation with Department of Physics and Astronomy,
> University of Victoria (astrowww.phys.uvic.ca).
>
> Programming affiliations with the FreeEOS equation-of-state implementation for
> stellar interiors (freeeos.sf.net); the Time Ephemerides project
> (timeephem.sf.net);
> PLplot scientific plotting software package (plplot.sf.net); the libLASi
> project
> (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the
> Linux Brochure
> Project (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
DISCLAIMER: This message is intended exclusively for the addressee(s) and may
contain confidential and privileged information. If you are not the intended
recipient please notify the sender immediately and destroy this message.
Unauthorized use, disclosure or copying of this message is strictly prohibited.
The foundation 'Stichting Deltares', which has its seat at Delft, The
Netherlands, Commercial Registration Number 41146461, is not liable in any way
whatsoever for consequences and/or damages resulting from the improper,
incomplete and untimely dispatch, receipt and/or content of this e-mail.
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel
