>> I don't think we have a test for CA exactly like Benjamin described, but
>> there are a load of self-tests in Base which it would be good for you to
>> run on your target if you haven't already done so. Just cd to the top of
>> your Base source tree and type 'make -s runtests'. Don't worry about
>> warning or error messages from the tests running, they are normal; just
>> look for summaries at the end of a group of tests that say something
>> like "Result: FAIL" and copy/paste the details of the failures that show
>> up near that line. Hopefully there won't be any, but...
Here is the output:
> Test Summary Report
> -------------------
> Breaktable.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> DBD.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Device.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Driver.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Function.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> macLib.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Menu.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Recfield.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Recordtype.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Registrar.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Snippets.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Variable.t (Wstat: 512 Tests: 0 Failed: 0)
> Non-zero exit status: 2
> Parse errors: No plan found in TAP output
> Files=12, Tests=0, 0 wallclock secs ( 0.03 usr 0.00 sys + 0.04 cusr 0.01 csys = 0.08 CPU)
> Result: FAIL
> Failed 12/12 test programs. 0/0 subtests failed.
> ringPointerTest.t .......... 1/37 epicsThreadSetPriority called by non epics thread epicsThreadSetPriority called by non epics thread
> dbPutLinkTest.t ............ 256/301 dbJLinkInit: lexical error: invalid char in json text.
> {"x":bbbb}
> (right here) ———^
> chfPluginTest.t ............ 1247/1433 chfConfigParseStart: plugin pvt alloc failed
Other tests are successful.
I hope, this helps you already
Best,
Simon
- Replies:
- Re: Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- References:
- Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- Re: Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- Re: Sequencer seem to skip states with EPICS 3.16.1 Ralph Lange
- Re: Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- Re: Sequencer seem to skip states with EPICS 3.16.1 Ralph Lange
- Re: Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- Re: Sequencer seem to skip states with EPICS 3.16.1 Benjamin Franksen
- Re: Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- Re: Sequencer seem to skip states with EPICS 3.16.1 Benjamin Franksen
- Re: Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- Re: Sequencer seem to skip states with EPICS 3.16.1 Andrew Johnson
- Navigate by Date:
- Prev:
quadEM R9-1 now available Mark Rivers
- Next:
FLIR 10Gbit Ethernet camera question Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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:
Re: Sequencer seem to skip states with EPICS 3.16.1 Andrew Johnson
- Next:
Re: Sequencer seem to skip states with EPICS 3.16.1 Simon Reiter
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|