on Sat May 31 2008, "troy d. straszheim"
wrote:
> It also knows which builds are pending, how many steps each contains,
> etc.
Don't we want to know that stuff? I do!
>>> Yeah, definitely. CTest does some of this but with mediocre resolution:
>>> it just reports Configure/Build/T
Hey Beman,
Beman Dawes wrote:
>
> I've been much happier with the current Boost regression reporting since it
> started reporting the SVN revision number. I'd hate to go back to a system
> that didn't report that.
>
No question about it, this kind of meta-information is crucial.
The snowblower
Hey Doug,
Very cool, none of that rather long mail ended up being contentious/confusing.
Smiles all round.
Doug Gregor wrote:
[snip]
> Well, I don't know if it's fragile or not (it's never caused problems
> for me), but there are other issues with not having testing targets be
> first-class cit
On Sun, Jun 1, 2008 at 12:20 PM, Doug Gregor <[EMAIL PROTECTED]> wrote:
> Hi Troy,
>
> On Sat, May 31, 2008 at 3:50 PM, troy d. straszheim <[EMAIL PROTECTED]>
> wrote:
>
> > 4. Tell how many *successful* build steps were executed. ctest
> > reports only failures. For instance, if I run an i
Hi Troy,
On Sat, May 31, 2008 at 3:50 PM, troy d. straszheim <[EMAIL PROTECTED]> wrote:
> When run, CTest reads these lists of tests in, runs them, and
> redirects the output to logfiles. It then must scrape results of
> builds/tests out of logfiles, tries (with varying degrees of success)
> to id
