<?xml version="1.0" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugzilla.globus.org/bugzilla/bugzilla.dtd">

<bugzilla version="3.2.3"
          urlbase="http://bugzilla.globus.org/bugzilla/"
          maintainer="bacon@mcs.anl.gov"
>

    <bug>
          <bug_id>2807</bug_id>
          
          <creation_ts>2005-02-22 19:33</creation_ts>
          <short_desc>execution aggregator source junit test needs some work</short_desc>
          <delta_ts>2008-02-12 11:11:19</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>MDS4</product>
          <component>wsrf_aggregator</component>
          <version>3.9.5</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>ASSIGNED</bug_status>
          
          
          
          
          
          <priority>P3</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>4.0</target_milestone>
          
          <blocked>5065</blocked>
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Mike Darcy">mdarcy@isi.edu</reporter>
          <assigned_to name="Neill Miller">neillm@mcs.anl.gov</assigned_to>
          <cc>laura@isi.edu</cc>
    
    <cc>mdarcy@isi.edu</cc>
    
    <cc>neillm@mcs.anl.gov</cc>

      

      
          <long_desc isprivate="0">
            <who name="Mike Darcy">mdarcy@isi.edu</who>
            <bug_when>2005-02-22 19:33:21</bug_when>
            <thetext>The execution aggregator source junit test needs to be fixed to actually run a 
valid executable and test the result.  

Validating the output of cat (or equivalent) on an xml sample file should 
suffice. Currently, the tests pass even though this is not actually happening.  
An error message is generated in the log, but what should probably happen is 
that a junit assertion be thrown.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Laura Pearlman">laura@isi.edu</who>
            <bug_when>2005-02-22 22:39:55</bug_when>
            <thetext>It turns out there is a sample executable (it&apos;s installed, but sort of hidden,
by default, and I haven&apos;t tried to test with it):  see
&quot;[]http://www-unix.globus.org/toolkit/docs/development/4.0-drafts/info/aggregator/developer/pingtest.html&quot;.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who name="Mike Darcy">mdarcy@isi.edu</who>
            <bug_when>2005-03-30 23:54:43</bug_when>
            <thetext>I committed code to the test to run the aggregator-test-exec.sh file that is 
now copied from G_L/etc/globus_wsrf_mds_aggregator to G_L/libexec/aggrexec. 
The test no longer should generate server side error messages on Linux.  

On Windows an error is still generated.  We will have to add code to 
ExecutionAggregatorSource if we want total Windows compatibility, so this bug 
maybe should be closed and reopened as an enhancement request for ExecAggr 
source on Windows.</thetext>
          </long_desc>
      
      

    </bug>

</bugzilla>