Boost Testing :
Subject: Re: [Boost-testing] [EXTERNAL] Re: Massive debug output in develop nightly testing
From: Beman Dawes (bdawes_at_[hidden])
Date: 2014-11-14 12:55:25
On Tue, Nov 11, 2014 at 10:03 PM, Belcourt, Kenneth <kbelco_at_[hidden]>
> On Nov 11, 2014, at 7:46 PM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> > Yes, it does look similar to output I saw. Didn't realize it would show
> up for others. But I don't know where it's coming from.
> > On Tue, Nov 11, 2014 at 8:27 PM, Belcourt, Kenneth <kbelco_at_[hidden]>
> > Hi,
> > Hereâs a snippet of output from the nightly testing process. I looks
> like someoneâs dumping pointer addresses, or something, and an awful lot of
> them at that. Rene, could this be related to the new testing capabilities
> youâre standing up? Any ideas?
> Looks like itâs coming from this commit Beman made a hour or so ago:
> He seems to have added an ostream overload that is getting picked up by
> the testing system.
> This one around line 100 in particular looks suspect:
> // Stream inserter
> template <class charT, class traits>
> friend std::basic_ostream<charT, traits>&
> operator<<(std::basic_ostream<charT, traits>& os, const T& x)
> return os << +x;
> Could this be it?
> I haven't been able to reproduce the problem for either Boost.Endian or
Boost.Timer running on Linux with gcc 4.8.2.
What platform and compiler are you seeing the problem with?