Subject: |
Re: libCom tests results 32 bit compatibility mode on windows vista 64 |
From: |
Andrew Johnson <[email protected]> |
To: |
[email protected] |
Date: |
Wed, 11 Feb 2009 12:41:55 -0600 |
Hi Jeff,
On Wednesday 11 February 2009 10:34:24 Jeff Hill wrote:
> Test Summary Report
> -------------------
> epicsUnitTestTest.t (Wstat: 0 Tests: 1 Failed: 1)
> Failed test: 1
> epicsStringTest.t (Wstat: 768 Tests: 1 Failed: 0)
> Non-zero exit status: 3
> Parse errors: No plan found in TAP output
> epicsMutexTest.t (Wstat: 0 Tests: 20 Failed: 1)
> Failed test: 20
> Parse errors: Bad plan. You planned 19 tests but ran 20.
> Files=22, Tests=1559, 420 wallclock secs ( 0.19 usr 0.06 sys + 0.53 cusr
> 0.9 csys = 1.70 CPU)
> Result: FAIL
> Failed 3/22 test programs. 2/1559 subtests failed.
Please manually run the programs O.<arch>/epicsStringTest.exe and
O.<arch>/epicsMutexTest.exe and post their output.
The failure in epicsUnitTestTest.t is just the line terminators, which
indicates that your version of perl is not expanding "\n" to the "\x0d\x0a"
that your C library is generating - are you using cygwin perl? This failure
doesn't worry me too much.
- Andrew
--
The best FOSS code is written to be read by other humans -- Harold Welte
- References:
- libCom tests results 32 bit compatibility mode on windows vista 64 Jeff Hill
- Navigate by Date:
- Prev:
libCom tests results 32 bit compatibility mode on windows vista 64 Jeff Hill
- Next:
Re: Base 3.14.11 Release Timetable Andrew Johnson
- Index:
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
libCom tests results 32 bit compatibility mode on windows vista 64 Jeff Hill
- Next:
Ideas for Codeathon Bernd Schoeneburg
- Index:
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|