15:09:46 <catohornet> #startmeeting Robot Happy Hour
15:09:46 <odl_meetbot> Meeting started Wed May 13 15:09:46 2015 UTC.  The chair is catohornet. Information about MeetBot at http://ci.openstack.org/meetbot.html.
15:09:46 <odl_meetbot> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:09:46 <odl_meetbot> The meeting name has been set to 'robot_happy_hour'
15:11:27 <PhilShea> catohornet: Good Morning
15:12:05 <zxiiro> howdy
15:14:52 <PhilShea> I have a question about where to find the python print statements that are called by my robot script.
15:15:31 <PhilShea> Does the output of those print statements go to anywhere I can find them?
15:16:03 <catohornet> Good morning
15:17:32 <PhilShea> Or would it be better to write those statements to a file?
15:17:48 <catohornet> Ah, Pybot doesn't write the output to a file
15:18:08 <catohornet> It would be better to write them to a file yes.
15:18:58 <catohornet> The only output files created are output.xml, report.html, and log.html.
15:19:39 <PhilShea> And any output from python functions that are called by robot, just go in the bit bucket, right?
15:20:29 <catohornet> You could create a keyword in your python script to log or 'print' the output in the procedure, then log that keyword in your test case to see the output.
15:20:50 <catohornet> pretty much
15:23:31 <PhilShea> Hmm. It might be kind of cool for troubleshooting, to put all the python debug output to a string, and return that to robot... That way it could be merged in the log.html file.
15:24:30 <PhilShea> I might experiment with that...
15:26:02 <PhilShea> I had another interesting issue yesterday.
15:26:47 <PhilShea> I'm running a suite of 16 tests, but the suite was failing on the 2nd test so I was trying troubleshoot that.
15:27:13 <PhilShea> The problem was the suite was taking 3 minutes to run, and you can't read the log until the run completes.
15:27:44 <PhilShea> It didn't seem there was a way to block comment out the tests that came after the 2nd test.
15:28:26 <PhilShea> Maybe the only was is to delete those test and recover them with git when done troubleshooting test 2.
15:28:51 <PhilShea> Any other ideas?
15:29:03 <catohornet> however
15:30:29 <vrpolak> PhilShea: > Any other ideas?  Good setup for self-plug: https://git.opendaylight.org/gerrit/#/c/19651/4/test/csit/libraries/FailFast.robot
15:31:52 <PhilShea> vrpolak: very cool. I like it
15:35:59 <catohornet> PhilShea: Nice
15:36:53 <catohornet> Have you tried using different log levels? According to the link you can get the data from your print statements.
15:37:56 <PhilShea> catohornet: I haven't. I'll give it a try, though.
16:03:10 <LuisGomez> jamoluhrsen and mgkwill
16:03:17 <jamoluhrsen> here
16:03:19 <mgkwill> Good Morning
16:03:41 <LuisGomez> hangout?
16:03:59 <jamoluhrsen> sure.
16:04:10 <catohornet> PhilShea: I'm trying the public_logging api to understand how it works.
16:04:13 <mgkwill> sounds good
16:05:18 <LuisGomez> https://plus.google.com/hangouts/_/g6esytv4mmrv6bsy26xwacvpgqa
16:05:33 <catohornet> #endmeeting