When I look at the results of a Beaker job, there's a lot of what I'm going to insensitively call "noise". Take, for example, one of my wireless tests. Each one has its own TESTOUT.log, and also submits a snippet of /var/log/wpa_supplicant.log. So, probably not even one of the "quietest" tests out there. Yet that test has the following logs in Beaker: /.task_beah_raw /wpa_supplicant.log /TESTOUT.log /task_beah_unexpected /task_output_stderr /task_log /task_output_stdout And then under a separate "./" subtest: l5-kernel-wireless-connection-to-WPA2-PEAP-AP-.log l5-kernel-wireless-connection-to-WPA2-PEAP-AP-.log Unfortunately, the visible names of these logs are truncated, and identical. Anyway, maybe we could hide the 7/9 of those logs per test that might not be very interesting to the end user?
Marian, Could you upload the beah debug logs into a subdirectory? pre-pend them with debug/ That way they will end up in a sub-diretory. I'll modify the UI to only show the dir, that way they are there for debugging but won't confuse others.
Done. http://git.fedorahosted.org/git/?p=beah.git;a=commit;h=1b06946fb33c7c0aab869fedc66521834aeb3ef4
Marian, shouldn't the bug be modified if the patch is commited? What's the deployment schedule?
It's half-patch only. WebUI support is in the queue - thus New.
WebUI support, low bug, scheduled for 0.6 - this isn't really a blocker for RHTS decomission. Moving to HotBeakerBugs tracker instead.
Year passed. Any update with this issue?
Logs are in debug directory and can easily be ignored if the end user doesn't need them.