gprofng not quite ready for prime time?

[Ruud van der Pas]

Hi Jan and José,

Thanks for your postings on this.

>> Earlier this year (iirc) some overly long lasting gas tests have been
>> disabled / altered. None of those took minutes. So I'm inclined to say
>> that anything which takes longer than a couple of seconds should be
>> off by default. Of course the threshold lowers as more tests are added,
>> unless a way is found to parallelize their running.
> 
> I think this is a sensible approach.

I think so too.

> We could have an additional check-expensive (or similar) target to run
> the full testsuite.

Right. Maybe not associate this with money though ;-) 

Perhaps something like "check-extensive" and issue a message how long
we expect those tests to run. Certainly also provide feedback. 

Nothing worse than a terminal prompt that doesn't re-appear for a
long long time after all!

We're very keen to address this and as a starting point, I just submitted
a bug report on this:

Bug 29470 - [test suite] The test suite should be made more flexible

https://sourceware.org/bugzilla/show_bug.cgi?id=29470

I also submitted a bug report against the version.texi file. In retrospect,
I think it is overkill to generate this file. We should just make sure
to update it with the new info when we release a doc patch.

This is the bug id by the way:

Bug 29465 - [docs] File version.texi is created in the binutils source directory 

https://sourceware.org/bugzilla/show_bug.cgi?id=29465

Kind regards, Ruud