[1.46.0] [units] test_output failing all release regression compilers
http://beta.boost.org/development/tests/release/developer/summary.html is looking pretty good for most libraries, but units test_output is failing all release regression compilers. Can we get a fix for this before the beta next week? Thanks, --Beman
On 1:59 PM, Beman Dawes wrote:
http://beta.boost.org/development/tests/release/developer/summary.html is looking pretty good for most libraries, but units test_output is failing all release regression compilers.
Looks like this needs to reopen: <https://svn.boost.org/trac/boost/ticket/4785>
On 1/17/2011 9:36 AM, Jim Bell wrote:
On 1:59 PM, Beman Dawes wrote:
http://beta.boost.org/development/tests/release/developer/summary.html is looking pretty good for most libraries, but units test_output is failing all release regression compilers. Looks like this needs to reopen: <https://svn.boost.org/trac/boost/ticket/4785>
Correction: needs to be taken from trunk to release.
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Monday, January 17, 2011 2:05 PM Subject: [boost] [1.46.0] [units] test_output failing all release regressioncompilers
http://beta.boost.org/development/tests/release/developer/summary.html is looking pretty good for most libraries, but units test_output is failing all release regression compilers.
Hi, I don't know if this is an easy task, but it will be great to have some statistics as: * the number of failing tests over le number of tests (3/76) (by tester) and * the number of failing testers by test Let me know if I can help in this task? Vicente
On 1:59 PM, vicente.botet wrote:
----- Original Message ----- From: "Beman Dawes" <bdawes@acm.org> To: "Boost Developers List" <boost@lists.boost.org> Sent: Monday, January 17, 2011 2:05 PM Subject: [boost] [1.46.0] [units] test_output failing all release regressioncompilers
http://beta.boost.org/development/tests/release/developer/summary.html is looking pretty good for most libraries, but units test_output is failing all release regression compilers. Hi,
I don't know if this is an easy task, but it will be great to have some statistics as: * the number of failing tests over le number of tests (3/76) (by tester) and * the number of failing testers by test
A diff view of the test matrix vs previous one would be super-cool, and one could build triggers from it. Or just that trigger view itself: newly-failed by platform.
On 1/17/2011 3:35 PM, vicente.botet wrote:
I don't know if this is an easy task, but it will be great to have some statistics as:
Nothing is an easy task when it comes to the current test report generation.. Even if you happen to be an uber-expert XSLT programmer. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
On 1:59 PM, Rene Rivera wrote:
On 1/17/2011 3:35 PM, vicente.botet wrote:
I don't know if this is an easy task, but it will be great to have some statistics as:
Nothing is an easy task when it comes to the current test report generation.. Even if you happen to be an uber-expert XSLT programmer.
Just curious: what's it written in? Python?
On 1/18/2011 11:19 AM, Jim Bell wrote:
On 1:59 PM, Rene Rivera wrote:
On 1/17/2011 3:35 PM, vicente.botet wrote:
I don't know if this is an easy task, but it will be great to have some statistics as:
Nothing is an easy task when it comes to the current test report generation.. Even if you happen to be an uber-expert XSLT programmer.
Just curious: what's it written in? Python?
I thought it was obvious from my statement above.. It's written in XSLT. Although the replacement I'm writing at the moment is in Python. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
----- Original Message ----- From: "Rene Rivera" <grafikrobot@gmail.com> To: <boost@lists.boost.org> Sent: Tuesday, January 18, 2011 5:34 PM Subject: Re: [boost] [1.46.0] [units] test_output failing allrelease regressioncompilers
On 1/17/2011 3:35 PM, vicente.botet wrote:
I don't know if this is an easy task, but it will be great to have some statistics as:
Nothing is an easy task when it comes to the current test report generation.. Even if you happen to be an uber-expert XSLT programmer.
How can I help? Vicente
On 1/18/2011 11:40 AM, vicente.botet wrote:
----- Original Message ----- From: "Rene Rivera"<grafikrobot@gmail.com> To:<boost@lists.boost.org> Sent: Tuesday, January 18, 2011 5:34 PM Subject: Re: [boost] [1.46.0] [units] test_output failing allrelease regressioncompilers
On 1/17/2011 3:35 PM, vicente.botet wrote:
I don't know if this is an easy task, but it will be great to have some statistics as:
Nothing is an easy task when it comes to the current test report generation.. Even if you happen to be an uber-expert XSLT programmer.
How can I help?
I guess I should have been more clear.. I'm not an uber-expert XSLT programmer. And have very little understanding of the details of the current XSLT regression results processing. And I'm not sure anyone does any more. So if you wanted to tackle the current XSLT reports, all I can do is point you to where they are: <http://svn.boost.org/svn/boost/trunk/tools/regression/xsl_reports/> And to say that, when I used to run those scripts, it was the "build_results.sh" wrapper that I used. Which in turn runs some other wrapper written in Python. Which then runs a variety of XSLT scripts. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
participants (4)
-
Beman Dawes -
Jim Bell -
Rene Rivera -
vicente.botet