<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>So chaps, I've found the commit that altered the IO handling in test_server (in fact, the addition of test_server_io). To clarify, prior to the addition of test_server_io, calls to ct:log/2 (and friends, e.g., ct:pal/2 and so on) would succeed even if no test was running and end up being handled as if they resided in before/after suite and/or before/after testcase functions. Now it seems that I've got to vet all the processes that might end up calling ct:log/2 (indirectly via my event manager) somehow, but there's no proper API to determine whether or not it is safe to do so. Having all my debug/info level testing framework logs emitted to the HTML files was a big reason for choosing common_test, so I'm loth to redirect them elsewhere. My code is basically doing lots of custom (data driven) setup/teardown before and after test suites and test cases, and even though some of this runs before (or during) the common_test test run is started, I *really* don't want to have to create yet another file location that needs to be inspected when tests fail. I'm also not keen on filling up stdio with lots of logging noise.</div><div><br></div><div>Any ideas how I can work around this situation without shooting myself in the head/foot? ;)</div><div><br></div><div>Cheers,</div><div>Tim</div><br><div><div>On 12 Jul 2013, at 08:36, Tim Watson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div bgcolor="#FFFFFF"><div>Hi Lukas, thanks for letting me know!</div><div><br></div><div>Cheers,</div><div>Tim</div><div><br>On 12 Jul 2013, at 08:29, Lukas Larsson <<a href="mailto:lukas@erlang.org">lukas@erlang.org</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
Hello Tim,<br>
<br>
Peter is currently away enjoying the sunny summer here in Sweden.
I'm sure he will get back to you when he comes back!<br>
<br>
Lukas<br>
<div class="moz-cite-prefix">On 12/07/13 02:03, Tim Watson wrote:<br>
</div>
<blockquote cite="mid:CALhYyxM-56eNnXFco4=hQDmVtfZ3U2ac35R1mPqTwGKfL4FA2w@mail.gmail.com" type="cite">
<div dir="ltr">On 1 July 2013 10:25, Tim Watson <span dir="ltr"><<a moz-do-not-send="true" href="mailto:watson.timothy@gmail.com" target="_blank">watson.timothy@gmail.com</a>></span>
wrote:> We should try to rule out that there's a bug that
causes test_server<br>
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">
> failure.<br>
<br>
</div>
How can I assist in verifying that?<br>
</blockquote>
<div><br>
</div>
<div>Any more news on this? Is there anything more I can do
to assist?<br>
</div>
<div><br>
</div>
<div>Cheers,<br>
Tim</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
erlang-bugs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:erlang-bugs@erlang.org">erlang-bugs@erlang.org</a>
<a class="moz-txt-link-freetext" href="http://erlang.org/mailman/listinfo/erlang-bugs">http://erlang.org/mailman/listinfo/erlang-bugs</a>
</pre>
</blockquote>
<br>
</div></blockquote></div></blockquote></div><br></body></html>