Re: [Boost-bugs] [Boost C++ Libraries] #11923: Boost Log backends fail silently on Ubuntu

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11923: Boost Log backends fail silently on Ubuntu
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2016-01-25 21:23:23


#11923: Boost Log backends fail silently on Ubuntu
-------------------------------+---------------------
  Reporter: lylemoffitt@… | Owner: andysem
      Type: Bugs | Status: closed
 Milestone: To Be Determined | Component: log
   Version: Boost 1.55.0 | Severity: Problem
Resolution: invalid | Keywords:
-------------------------------+---------------------

Comment (by Lyle Moffitt <lylemoffitt@…>):

 1. What system are you testing on? Is is Ubuntu 14.04? This problem is
 likely specific to at the very least that distro.
 2. I don't think you looked at the source code at all.. Both sinks are
 set to `auto_flush=true`.
 3. If the problem were that {{{"some of the log records are left in the
 queue unprocessed when the test terminates"}}}, then it would be easy to
 prove it so. Here are some ways you could do that:
    a. You could simply add a`log_data::file_sink->flush()` command before
 exiting `main()`.
    b. You could remove the filter step to prevent the queue from being
 blocked.
    c. You could remove the async sink from the logger and just use the
 synchronous terminal sink, which would not be blocked.
 4. Here are some reasons why I don't think your hypotheses is correct:
    a. The `test_file_backend` is setup to create a file and write a header
 to it before ''any'' logging is done.
    b. I tried calling `flush()` for both sinks before exiting `main()`. If
 the messages were stuck in the queue somehow, then this would have
 prevented the program from exiting at all, since both methods a defined to
 block until the queue is empty.
    c. I am in fact using 2 sinks (async'd file and sync'd terminal). Your
 explanation completely misses the latter.

 TL;DR: Your explanation is just plain wrong.

 ----
 I took a lot of time to make this as simple an example as possible while
 still retaining the essence of the problem. I took pains to document and
 format a bug report to help you out. The fact that you barely looked at
 the code and then gave me a half-assed answer is frankly insulting. If you
 aren't going to take this seriously, please pass this bug to someone who
 will.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/11923#comment:6>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:19 UTC