All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junxiao Bi <junxiao.bi@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 02/17] Single Run: kernel building is little broken now
Date: Mon, 13 Mar 2017 16:12:42 +0800	[thread overview]
Message-ID: <c950b2f6-575f-545c-a7d3-bd99ba056271@oracle.com> (raw)
In-Reply-To: <1481606975-13186-3-git-send-email-zren@suse.com>

On 12/13/2016 01:29 PM, Eric Ren wrote:
> Only check kernel source if we specify "buildkernel" test case.
> The original kernel source web-link cannot be reached,
> so give a new link instead but the md5sum check is missing
> now.
> 
> Signed-off-by: Eric Ren <zren@suse.com>
> ---
>  programs/python_common/single_run-WIP.sh | 56 ++++++++++++++++----------------
>  1 file changed, 28 insertions(+), 28 deletions(-)
> 
> diff --git a/programs/python_common/single_run-WIP.sh b/programs/python_common/single_run-WIP.sh
> index fe0056c..61008d8 100755
> --- a/programs/python_common/single_run-WIP.sh
> +++ b/programs/python_common/single_run-WIP.sh
> @@ -20,9 +20,9 @@ WGET=`which wget`
>  WHOAMI=`which whoami`
>  SED=`which sed`
>  
> -DWNLD_PATH="http://oss.oracle.com/~smushran/ocfs2-test"
> -KERNEL_TARBALL="linux-kernel.tar.gz"
> -KERNEL_TARBALL_CHECK="${KERNEL_TARBALL}.md5sum"
> +DWNLD_PATH="https://cdn.kernel.org/pub/linux/kernel/v3.x/"
> +KERNEL_TARBALL="linux-3.2.80.tar.xz"
> +#KERNEL_TARBALL_CHECK="${KERNEL_TARBALL}.md5sum"

Can we compute the md5sum manually and put it here?

Thanks,
Junxiao.

>  USERID=`${WHOAMI}`
>  
>  DEBUGFS_BIN="${SUDO} `which debugfs.ocfs2`"
> @@ -85,7 +85,7 @@ get_bits()
>  # get_kernel_source $LOGDIR $DWNLD_PATH $KERNEL_TARBALL $KERNEL_TARBALL_CHECK
>  get_kernel_source()
>  {
> -	if [ "$#" -lt "4" ]; then
> +	if [ "$#" -lt "3" ]; then
>  		${ECHO} "Error in get_kernel_source()"
>  		exit 1
>  	fi
> @@ -93,18 +93,18 @@ get_kernel_source()
>  	logdir=$1
>  	dwnld_path=$2
>  	kernel_tarball=$3
> -	kernel_tarball_check=$4
> +	#kernel_tarball_check=$4
>  
>  	cd ${logdir}
>  
>  	outlog=get_kernel_source.log
>  
> -	${WGET} -o ${outlog} ${dwnld_path}/${kernel_tarball_check}
> -	if [ $? -ne 0 ]; then
> -		${ECHO} "ERROR downloading ${dwnld_path}/${kernel_tarball_check}"
> -		cd -
> -		exit 1
> -	fi
> +#	${WGET} -o ${outlog} ${dwnld_path}/${kernel_tarball_check}
> +#	if [ $? -ne 0 ]; then
> +#		${ECHO} "ERROR downloading ${dwnld_path}/${kernel_tarball_check}"
> +#		cd -
> +#		exit 1
> +#	fi
>  
>  	${WGET} -a ${outlog} ${dwnld_path}/${kernel_tarball}
>  	if [ $? -ne 0 ]; then
> @@ -113,13 +113,13 @@ get_kernel_source()
>  		exit 1
>  	fi
>  
> -	${MD5SUM} -c ${kernel_tarball_check} >>${outlog} 2>&1
> -	if [ $? -ne 0 ]; then
> -		${ECHO} "ERROR ${kernel_tarball_check} check failed"
> -		cd -
> -		exit 1
> -	fi
> -	cd -
> +#	${MD5SUM} -c ${kernel_tarball_check} >>${outlog} 2>&1
> +#	if [ $? -ne 0 ]; then
> +#		${ECHO} "ERROR ${kernel_tarball_check} check failed"
> +#		cd -
> +#		exit 1
> +#	fi
> +#	cd -
>  }
>  
>  # do_format() ${BLOCKSIZE} ${CLUSTERSIZE} ${FEATURES} ${DEVICE}
> @@ -1012,16 +1012,6 @@ LOGFILE=${LOGDIR}/single_run.log
>  
>  do_mkdir ${LOGDIR}
>  
> -if [ -z ${KERNELSRC} ]; then
> -	get_kernel_source $LOGDIR $DWNLD_PATH $KERNEL_TARBALL $KERNEL_TARBALL_CHECK
> -	KERNELSRC=${LOGDIR}/${KERNEL_TARBALL}
> -fi
> -
> -if [ ! -f ${KERNELSRC} ]; then
> -	${ECHO} "No kernel source"
> -	usage
> -fi
> -
>  STARTRUN=$(date +%s)
>  log_message "*** Start Single Node test ***"
>  
> @@ -1058,6 +1048,16 @@ for tc in `${ECHO} ${TESTCASES} | ${SED} "s:,: :g"`; do
>  	fi
>  
>  	if [ "$tc"X = "buildkernel"X -o "$tc"X = "all"X ];then
> +		if [ -z ${KERNELSRC} ]; then
> +			get_kernel_source $LOGDIR $DWNLD_PATH $KERNEL_TARBALL #$KERNEL_TARBALL_CHECK
> +			KERNELSRC=${LOGDIR}/${KERNEL_TARBALL}
> +		fi
> +
> +		if [ ! -f ${KERNELSRC} ]; then
> +			${ECHO} "No kernel source"
> +			usage
> +		fi
> +
>  		run_buildkernel ${LOGDIR} ${DEVICE} ${MOUNTPOINT} ${KERNELSRC}
>  	fi
>  
> 

  reply	other threads:[~2017-03-13  8:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13  5:29 [Ocfs2-devel] [PATCH 00/17] ocfs2-test: misc improvements and trivial fixes Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 01/17] ocfs2 test: correct the check on testcase if supported Eric Ren
2017-03-13  8:11   ` Junxiao Bi
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 02/17] Single Run: kernel building is little broken now Eric Ren
2017-03-13  8:12   ` Junxiao Bi [this message]
2017-03-13  8:29     ` Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 03/17] Trivial: better not to depend on where we issue testing Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 04/17] Trivial: fix a typo mistake Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 05/17] Trivial: fix checking empty return value Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 06/17] multi_mmap: make log messages go to right place Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 07/17] lvb_torture: failed when pcmk is used as cluster stack Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 08/17] multiple node: pass cross_delete the right log file Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 09/17] Single run: make blocksize and clustersize as parameters Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 10/17] Multiple " Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 11/17] discontig bg: " Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 12/17] Add two cluster-aware parameters: cluster stack and cluster name Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 13/17] Save punch_hole details into logfile for debugging convenience Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 14/17] Fix openmpi warning by specifying proper slot number Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 15/17] Handle the case when a symbolic link device is given Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 16/17] inline data: fix build error Eric Ren
2016-12-13  5:29 ` [Ocfs2-devel] [PATCH 17/17] discontig bg: give single and multiple node test different log file name Eric Ren
2017-01-05  6:30 ` [Ocfs2-devel] [PATCH 00/17] ocfs2-test: misc improvements and trivial fixes Eric Ren

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=c950b2f6-575f-545c-a7d3-bd99ba056271@oracle.com \
    --to=junxiao.bi@oracle.com \
    --cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.