WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH][XM-TEST] correct inconsistent reporting in xm-te

To: marvel@xxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH][XM-TEST] correct inconsistent reporting in xm-test
From: Dan Smith <danms@xxxxxxxxxx>
Date: Fri, 17 Mar 2006 06:35:12 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 17 Mar 2006 14:36:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1142570610.3629.25.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> (woody marvel's message of "Thu, 16 Mar 2006 20:43:29 -0800")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1142570610.3629.25.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.4 (gnu/linux)
>  submit_report() {
> -
>      reportfile=$1
> -
> -    ./lib/XmTestReport/Report.py $reportfile
> +    if [ "$GROUPENTERED" = "default" ];then
> +       ./lib/XmTestReport/Report.py $reportfile
> +    else
> +       echo "No report submitted for $REPORT, requires a default group run."
> +    fi
>  }

Why change the semantics of submit_report() from "submit a report" to
"maybe submit a report" ??  The script already has a method for
disabling the report submission based on certain criteria.  You should
use that to achieve the desired behavior.
 
>  make_environment_report() {
>      os=$1
>      prog=$2
> +    rm -f $REPORT"*" > /dev/null 2>&1
>      if ! ./lib/XmTestReport/OSReport.py > $os; then
>       echo "Unable to generate clean OSReport"
>       echo "Take a look at $os"

I think this is bad because if we later decide to re-order the
reports, make_environment_report() will nuke the report file in the
middle.  This should be done at the top level.

> @@ -280,5 +280,5 @@
>       echo "No such file: $XMLREPORT"
>       exit 1
>      fi
> -    submit_report $XMLREPORT
> -fi
> +    submit_report $XMLREPORT 
> +fi

Why is this hunk in your patch?

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx

Attachment: pgpFKcQJYPtlx.pgp
Description: PGP signature

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>