<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 3, 2018 at 3:41 PM, Kostis Sagonas <span dir="ltr"><<a href="mailto:kostis@cs.ntua.gr" target="_blank">kostis@cs.ntua.gr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 05/03/2018 03:29 PM, Lukas Larsson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
<br>
On Thu, May 3, 2018 at 3:07 PM, Max Lapshin <<a href="mailto:max.lapshin@gmail.com" target="_blank">max.lapshin@gmail.com</a> <mailto:<a href="mailto:max.lapshin@gmail.com" target="_blank">max.lapshin@gmail.com</a>><wbr>> wrote:<br>
<br>
Not sure about new logging:<br>
<br></span>
...<br>
<br>
From<br>
<a href="http://erlang.org/documentation/doc-10.0-rc1/lib/kernel-6.0/doc/html/error_logger.html" rel="noreferrer" target="_blank">http://erlang.org/documentatio<wbr>n/doc-10.0-rc1/lib/kernel-6.0/<wbr>doc/html/error_logger.html</a><span class=""><br>
<<a href="http://erlang.org/documentation/doc-10.0-rc1/lib/kernel-6.0/doc/html/error_logger.html" rel="noreferrer" target="_blank">http://erlang.org/documentati<wbr>on/doc-10.0-rc1/lib/kernel-6.<wbr>0/doc/html/error_logger.html</a>> I do not see that error_logger is no more with us.<br>
<br>
Is it a existing process or it is completely abandoned?<br>
<br>
The error_logger event handler is started lazily when the first error_logger:add_report_handle<wbr>r call is done. So the new logging framework does not use the error_logger process, but it is started if legacy code uses it. All calls to error_logger:*_report/msg are redirected to logger which then decides what to do with them.<br>
</span></blockquote>
<br>
Something has clearly changed in the behaviour of the error logger in ways that I am not sure I completely understand.<br>
<br>
I have a simple script to run the HiPE tests which looks as follows:<br>
==============================<wbr>=======<br>
#! /bin/sh<br>
<br>
export ERL_TOP=$PWD<br>
export PATH=$ERL_TOP/bin:$PATH<br>
<br>
TDIR=/tmp/otp_tests<br>
<br>
rm -rf $TDIR<br>
./otp_build tests $TDIR<br>
cd $TDIR<br>
ct_run -dir hipe_test<br>
==============================<wbr>=======<br>
<br>
Till last Friday, this script was running fine, even on master. Since Friday when a lot of changes about the new 'logger' were merged, this script produces tons of lines of the form:<br>
<br>
=ERROR REPORT==== 3-May-2018::15:38:47.765241 ===<br>
Error in process <0.1524.0> on node ct@MACHINE with exit value:<br>
{timeout_value,[{basic_excepti<wbr>ons,bad_guy,2,[]}]}<br>
<br>
=WARNING REPORT==== 3-May-2018::15:38:51.663313 ===<br>
Process <0.2680.0> on node 'ct@MACHINE' enabled access to the emulator internal state.<br>
NOTE: This is an erts internal test feature and should *only* be used by OTP test-suites.<br>
<br>
<br>
How does one suppress these?</blockquote><div><br></div><div>There seems to be some bug in the cth_log_redirect. You should be able to do "ct_run -kernel logger_dest silent -dir hipe_test" to work around it for now. We'll fix the bug.</div><div><br></div><div>Lukas</div></div></div></div>