On 05/16/2017 01:49 AM, Ralph Lange wrote:
> As it is not related to any code, I would add it to all branches that we
> build using CI: 3.14/3.15/3.16
Committed and merged up.
Don't forget to install the Perl XML::Generator module when using this...
> Related issue:
> Can we make the tap or xunit targets also print the summary line
> (Result: PASS etc.) on stdout, i.e. add the commands that Michael uses
> on Travis? (find .-name '*.tap'-print0 |xargs -0 -n1 prove -e cat -f).
> That would make grep'ing the make output (scrolling back or by script) a
> lot easier when running the tap/xunit style.
I have been adding an equivalent (prove --failure) to the end of my
build scripts, let me know if you find any specific jobs that I've missed.
- Andrew
--
Arguing for surveillance because you have nothing to hide is no
different than making the claim, "I don't care about freedom of
speech because I have nothing to say." -- Edward Snowdon
- References:
- Interest in JUnit xml Test Results? Andrew Johnson
- Re: Interest in JUnit xml Test Results? Ralph Lange
- Navigate by Date:
- Prev:
Re: Interest in JUnit xml Test Results? Ralph Lange
- Next:
Build failed in Jenkins: epics-base-3.16-mac-test #102 APS Jenkins
- 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:
Re: Interest in JUnit xml Test Results? Ralph Lange
- Next:
Build failed in Jenkins: epics-base-3.16-mac-test #102 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|