From: Laszlo Ersek <lersek@redhat.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, aliguori@us.ibm.com, qemu-devel@nongnu.org,
blauwirbel@gmail.com, alex.williamson@redhat.com,
stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] script: git script to compile every commit in a range of commits
Date: Thu, 06 Jun 2013 10:58:25 +0200 [thread overview]
Message-ID: <51B04F31.4040908@redhat.com> (raw)
In-Reply-To: <efeda2a331c449f05c5c09b8ccb29ff1980199ab.1370018258.git.jcody@redhat.com>
comments below
On 05/31/13 18:39, Jeff Cody wrote:
> +usage() {
> + echo ""
> + echo "$0 [OPTIONS]"
> + echo "$desc"
> + echo ""
> + echo "OPTIONS:"
> + echo " -r git range
> + optional; default is '$range'
> + "
> + echo " -c configure options
> + optional; default is '$config_opt'
> + "
> + echo " -m make options
> + optional; default is '$make_opt'
> + "
> + echo " -d log dir
> + optional; default is '$logdir'
> + "
> + echo " -l log filename
> + optional; default is output-PROCID, where PROCID is the bash process id
> + note: you may specify a full path for the log filename here, and exclude the
> + -d option.
> + "
> + echo " -f force a git reset and clean
> + this will cause a 'git reset --hard; git clean -fdx' to be run between checkouts.
> + !! WARNING: This may cause data loss in your git tree.
> + READ THE git-clean and git-reset man pages and make
> + sure you understand the implications of
> + 'git clean -fdx' and 'git reset --hard' before using !!
> + "
> + echo " -h help"
> +}
Sorry for not noticing this before: is there any reason for the trailing
spaces on most lines in the usage text?
Plus I suggest lower-casing the "THE" in "READ THE".
> +
> +while getopts ":r:c:m:l:d:hf" opt
> +do
> + case $opt in
> + r) range=$OPTARG
> + ;;
> + c) config_opt=$OPTARG
> + ;;
> + m) make_opt=$OPTARG
> + ;;
> + d) logdir=$OPTARG
> + ;;
> + l) logfile=$OPTARG
> + ;;
> + f) force_clean='y'
> + ;;
> + h) usage
> + exit
> + ;;
> + \?) echo "Unknown option: -$OPTARG" >&2
> + usage
> + exit 1
> + ;;
> + esac
> +done
> +
> +# append a '/' to logdir if $logdir was specified without one
> +[[ -n "$logdir" ]] && [[ ${logdir:${#logdir}-1} != "/" ]] && logdir="${logdir}/"
> +
> +logfile="${logdir}${logfile}"
> +
> +head=`git rev-parse HEAD`
> +total=`git rev-list "$range" |wc -l`
> +
> +echo "log output: $logfile"
> +
> +rm -f "$logfile"
rm -f -- "$logfile" is safer, but I doubt anyone would pass a pathname
starting with "-"...
> +date > "$logfile"
> +echo "git compile check for $range." >> "$logfile"
> +echo "* configure options='$config_opt'" >> "$logfile"
> +echo "* make options='$make_opt'" >> "$logfile"
> +echo "Performing a test compile on $total patches" | tee -a "$logfile"
> +echo "-------------------------------------------------------------" >> "$logfile"
> +echo "" | tee -a "$logfile"
> +
> +clean_repo() {
> + if [[ $force_clean == 'y' ]]
> + then
> + git reset --hard >> "$logfile" 2>&1 || true
> + git clean -fdx -e "$logfile" >> "$logfile" 2>&1 || true
> + fi
> +}
Does "-e" mean "except"? It's not supported on RHEL-6.
> +
> +# we want to cleanup and return the git tree back to the previous head
> +trap cleanup EXIT
> +
> +cleanup() {
> + echo ""
> + echo -n "Cleaning up..."
> + clean_repo
> + git checkout $head > /dev/null 2>&1
> + echo "done."
> +}
> +
> +cnt=1
> +# don't pipe the git job into read, to avoid subshells
> +while read hash
> +do
> + txt=`git log --pretty=tformat:"%h: %s" $hash^!`
> + echo "${cnt}/${total}: compiling: $txt" | tee -a "$logfile"
> + let cnt=$cnt+1;
> + echo "####################" >> "$logfile"
> + clean_repo
> + make clean > /dev/null 2>&1 || true
> + git checkout $hash >> "$logfile" 2>&1 && \
> + ./configure $config_opt >> "$logfile" 2>&1 && \
> + make $make_opt >> "$logfile" 2>&1 ||
> + (
> + echo "" | tee -a "$logfile"
> + echo "ERROR: commit $hash failed to build!" | tee -a "$logfile"
> + git show --stat $hash | tee -a "$logfile"
> + exit 1
> + )
> +done < <(git log $range --pretty=tformat:"%H" --reverse)
> +
> +echo "
> +All patches in $range compiled successfully!" | tee -a "$logfile"
> +exit 0
>
I think my remarks are not important, the script should work in any
practical environment. We should get this merged and small fixes can be
posted incrementally if needed.
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
next prev parent reply other threads:[~2013-06-06 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 16:39 [Qemu-devel] [PATCH] script: git script to compile every commit in a range of commits Jeff Cody
2013-06-06 8:58 ` Laszlo Ersek [this message]
2013-06-07 14:44 ` Jeff Cody
2013-06-07 15:40 ` Laszlo Ersek
2013-06-07 16:51 ` Anthony Liguori
2013-06-07 20:30 ` Jeff Cody
2013-06-10 9:41 ` Peter Crosthwaite
2013-06-07 16:36 ` Peter Crosthwaite
2013-06-07 19:13 ` Jeff Cody
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51B04F31.4040908@redhat.com \
--to=lersek@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=jcody@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).