Re: [boost] Boost regression notification (2006-09-22 [RC_1_34_0])

From: Lars Gullik Bjønnes (larsbj_at_[hidden])
Date: 2006-09-23 18:08:31

David Abrahams <dave_at_[hidden]> writes:

| larsbj_at_[hidden] (Lars Gullik Bjønnes) writes:
| 
| > David Abrahams <dave_at_[hidden]> writes:
| >
| > | larsbj_at_[hidden] (Lars Gullik Bjønnes) writes:
| > | 
| > | > Douglas Gregor <dgregor_at_[hidden]> writes:
| > | >
| > | > | Boost Regression test failures
| > | > | Report time: 2006-09-22T12:06:02Z
| > | > | 
| > | > | This report lists all regression test failures on release platforms.
| > | > | 
| > | > | Detailed report:
| > | > |   http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/issues.html
| > | > | 
| > | > | 293 failures in 14 libraries
| > | >
| > | > This number seems to just be going up lately. 
| > | 
| > | Really?  I've been knocking it down hard, and making steady progress
| > | on _my_ problems, anyway.   A reconfiguration of test
| > | machines at OSL caused the entire Boost.Python library to start
| > | failing on one of their machines yesterday, but the problem has been
| > | diagnosed.  It's a momentary glitch, I assure you.
| >
| > It is not the momentary glitches that worry. Perhaps it is the
| > "buisiness as usual" on the mailinglist and not the all-out focus on
| > getting the 1.34 release out that worry me most. 
| 
| That's a worry, I agree.  What can we do to fix that?

I know that this has been discussed, but I still think that putting
the cvs repo in a "regressions only" mode would have helped.

(And wait with the release branch until trunk is in a fairly regression free
state)

btw. I'll try to do a regression run on my platform now (x86_64 gcc
4.1.1) and see if there are still issues there.

-- 
	Lgb