[opa-nightly-tests] jam OPA_Daily_Tests_0417Thu_FAILED!!!
Albert Cheng
acheng at hdfgroup.org
Fri Apr 18 12:26:01 CDT 2014
I noticed emu's clock was more than 10 seconds but less than a minute different from Jam.
That was two days ago (the day when quail failed daily test because of NFS failures that due to clock difference).
I thought Emu was within tolerance. Did the clock drift even further apart?
On Apr 18, 2014, at 6:30 AM, Larry Knox <lrknox at hdfgroup.org> wrote:
> Emu system clock is out of sync. We'll get it corrected today.
>
> Larry
>
> -----Original Message-----
> From: opa-nightly-tests-bounces at lists.mcs.anl.gov [mailto:opa-nightly-tests-bounces at lists.mcs.anl.gov] On Behalf Of HDF Tester
> Sent: Thursday, April 17, 2014 11:24 PM
> To: opa-nightly-tests at lists.mcs.anl.gov
> Subject: [opa-nightly-tests] jam OPA_Daily_Tests_0417Thu_FAILED!!!
>
> *** OPA Tests on 0417Thu ***
> =============================
> Tests Summary
> =============================
> ****FAILED emu: standard op-configure --prefix=/mnt/scr1/pre-release/opa/emu32 deploy emu32****
>
> PASSED jam: standard op-configure --prefix=/mnt/scr1/pre-release/opa/jam deploy jam PASSED kite: standard op-configure --prefix=/mnt/scr1/pre-release/opa/kite deploy kite PASSED koala: standard op-configure --prefix=/mnt/scr1/pre-release/opa/koala deploy koala PASSED ostrich: standard op-configure --prefix=/mnt/scr1/pre-release/opa/ostrich deploy ostrich PASSED platypus: standard op-configure --prefix=/mnt/scr1/pre-release/opa/platypus deploy platypus
>
> =============================
> Tests Time Summary
> =============================
> emu: Ran 1(0/1/0) tests, Grand total test time = 0m 2s
> koala: Ran 1(1/0/0) tests, Grand total test time = 0m 33s
> platypus: Ran 1(1/0/0) tests, Grand total test time = 0m 46s
> jam: Ran 1(1/0/0) tests, Grand total test time = 0m 58s
> kite: Ran 1(1/0/0) tests, Grand total test time = 0m 55s
> ostrich: Ran 1(1/0/0) tests, Grand total test time = 1m 39s
> jam: Ran 6(0/0/0) hosts, Grand total test time = 2m 45s
>
>
> =============================
> Timekeeper log
> =============================
> Timekeeper started at Thu Apr 17 23:21:49 CDT 2014 Timekeeper sleeping for 720 seconds
>
>
> =============================
> Tests Failures
> =============================
> =========================
> Dumping logfile of emu: standard op-configure --prefix=/mnt/scr1/pre-release/opa/emu32 deploy emu32 Last 50 lines of /mnt/scr1/SnapTest/snapshots-opa/log/emu_0417Thu_2321
> =========================
> A__z="*SHLVL
> CCACHE_DISABLE=yes
> CVSROOT=/mnt/hdf/cvs
> EC2_CERT=/home/hdftest/.ec2/cert-6HKISUOM3HT2PWDQB4PLG67KTWOVVKOK.pem
> EC2_HOME=/mnt/hdf/ec2-api-tools
> EC2_PRIVATE_KEY=/home/hdftest/.ec2/pk-6HKISUOM3HT2PWDQB4PLG67KTWOVVKOK.pem
> GROUP=hdf
> HDF5TestExpress=yes
> HOME=/home/hdftest
> HOST=emu.hdfgroup.uiuc.edu
> HOSTTYPE=sun4
> JAVA_HOME=/usr/lib/jvm/jre-1.6.0
> LANG=en_US.UTF-8
> LC_ALL=
> LC_COLLATE=
> LC_CTYPE=
> LC_MESSAGES=
> LC_MONETARY=
> LC_NUMERIC=
> LC_TIME=
> LOGNAME=hdftest
> MACHTYPE=sparc
> MAIL=/var/mail/hdftest
> MAKE=gmake -j 8
> NLSPATH=/usr/share/locale/%L/LC_MESSAGES/%N.cat
> OSTYPE=solaris
> PATH=/home/hdftest/bin:/usr/hdf/bin:/home/hdftest/bin:/usr/hdf/bin:/usr/bin:/usr/sbin:/opt/solarisstudio/bin:/opt/cmake/bin:/opt/svn/bin:/mnt/hdf/ec2-api-tools/bin
> PWD=/mnt/scr1/SnapTest/snapshots-opa
> REMOTEHOST=
> SET_PATH=yes
> SHELL=/bin/tcsh
> SHLVL=3
> SSH_CLIENT=72.36.68.242 42514 22
> SSH_CONNECTION=72.36.68.242 42514 72.36.68.177 22 SVNROOT=http://svn.hdfgroup.uiuc.edu
> TZ=localtime
> USER=hdftest
> VENDOR=sun
> ===Done Dumping environment variables after option parsing === ===== Run Tests: Thursday, April 17, 2014 11:21:44 PM CDT ===== Remove contents of emu.
>
> diff: /home/hdftest/snapshots-opa/previous/MANIFEST: No such file or directory ===== configure: Thursday, April 17, 2014 11:21:44 PM CDT ===== checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether build environment is sane... configure: error: newly created file is older than distributed files!
> Check your system clock
> Failed running configure
> ===== Exit bin/snapshot with status=1: Thursday, April 17, 2014 11:21:45 PM CDT ===== Thursday, April 17, 2014 11:21:45 PM CDT ========================= Dumping done =========================
>
> Runtest did not exit normally.
>
> =============================
> Watchers List
> =============================
> OPA Daily test features/platforms watchers and procedure
> ---------------------------------------------------------
>
> Procedure:
> The watcher will investigate and report the cause of failure by 11am.
> The developer who checked in the error code may report so by then too.
> The watcher or the developer should get the failure fixed and report it by 3pm.
>
>
> Watcher for OPA: Neil
>
>
> ---
> updated: 2009/05/05
>
>
More information about the opa-nightly-tests
mailing list