ok I see, thanks for the explanation Gerhard.
greg. 2011/2/25 Gerhard Lausser <gerhard.laus...@consol.de> > Hi, > > you only see livestatus output, because there is only one resultfile. > Normally, nosetests are executed like: > > nosetests --with-xunit list_of_py_files > > Then you'll get an output file nosetests.xml which contains information on > every single python-file from the list. But with Shinken you'll get > strange errors. (try it with cd test; nosetests --with-xunit > the_files_from_jenkins/shorttests.txt) > That's why we said, don't spend much time on this issue and run the > testscripts separately. > So now the Shinken test looks like > > for f in list_of_py_files > nosetests --with-xunit f > > which means that after every loop you get another nosetests.xml file which > contains only the data for file f. > As test_lifestatus is the last one in the list, you see lifestatus' > nosetests.xml as hudson's result. > > Gerhard > > > -----Ursprüngliche Nachricht----- > > Von: Grégory Starck [mailto:g.sta...@gmail.com] > > Gesendet: Freitag, 25. Februar 2011 09:53 > > An: shinken-devel@lists.sourceforge.net > > Betreff: [Shinken-devel] jobs tests > > > > for my info, on : > > > > http://shinken-monitoring.de:8080/job/Shinken/363/testReport/ > > > > is it normal that there is only test_livestatus for a long > > time already on that specific job/task ? > > > > greg. > > > > > >
------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
