"Beman Dawes" <bdawes@acm.org> wrote in message news:47153D34.8070105@acm.org...
Gennadiy Rozental wrote:
"Beman Dawes" <bdawes@acm.org> wrote in message news:47151E0B.4090506@acm.org...
The Win32 smoke test at 40095 is now available. See http://mysite.verizon.net/beman/win32-trunk-results.html
These tells me nothing.
Here is how you use the smoke tests:
[...] When this procedure was esteblished? Is it described somewhere on site?
It looks to me like Gennadiy should run the full test suite locally before committing changes to trunk. That would have certainly detected last night's snafu before it happened.
I already spend hours on testing before I do any commit. Waiting days for the full test to complete will make it impossible for me to make any changes.
For one compiler, a full VC++ test takes about two hours on a modern desktop machine. But an incremental test takes less; as short as 5 minutes for small changes. The changes you made last night caused my machine to take about 50 minutes to cycle through the full set of tests.
My computer is not as powerfull. I would expect at least several hours if not longer for the full regressiontest run. And than multiply it by at least 6.
Most developers don't have to go to that extreme, but Boost.Test is special because so many of our developers depend on it.
And it still will leave a lot of room for possible portability failures, since I can't run on all the *unix platforms.
We aren't expecting every platform to be tested. But there is no excuse for committing code that breaks a lot of libraries for your personal desktop platform. And then no excuse for breaking Win32/VC++ or Linux/GCC for more than an hour or so, since we test those for you with tests cycling as often as every 20 minutes.
Well. I retested everything again. Gcc with mignw and cygwin, msvc 8.0 7.1, cw and intel. I'll give it another try and will follow procedure above. Gennadiy