trunk tests failing

[K. Noel Belcourt]

#     /incoming/trunk/processed/merged/Debian-Sid.xml: run
#     target doesn't exists, building
#             Merging "/incoming/trunk/processed/Debian-Sid.xml" with  
expected results...
#             xsltproc -o "/sierra/Src/kbelco/boost/reporting/trunk/
incoming/trunk/processed/merged/Debian-Sid.xml" --param source  
"'trunk'"  --param expected_results_file "'/sierra/Src/kbelco/boost/
reporting/boost/status/expected_results.xml'"  --param  
failures_markup_file "'/sierra/Src/kbelco/boost/reporting/boost/status/
explicit-failures-markup.xml'"  "/sierra/Src/kbelco/boost/reporting/
boost/tools/regression/xsl_reports/xsl/v2/add_expected_results.xsl"  "/
sierra/Src/kbelco/boost/reporting/trunk/incoming/trunk/processed/
Debian-Sid-trimmed.xml"

                         Unknown test type "run_mpi"

Any ideas?

-- Noel


_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[K. Noel Belcourt]

On Aug 8, 2009, at 1:52 PM, Belcourt, Kenneth wrote:

> #     /incoming/trunk/processed/merged/Debian-Sid.xml: run
> #     target doesn't exists, building
> #             Merging "/incoming/trunk/processed/Debian-Sid.xml" with
> expected results...
> #             xsltproc -o "/sierra/Src/kbelco/boost/reporting/trunk/
> incoming/trunk/processed/merged/Debian-Sid.xml" --param source
> "'trunk'"  --param expected_results_file "'/sierra/Src/kbelco/boost/
> reporting/boost/status/expected_results.xml'"  --param
> failures_markup_file "'/sierra/Src/kbelco/boost/reporting/boost/
> status/
> explicit-failures-markup.xml'"  "/sierra/Src/kbelco/boost/reporting/
> boost/tools/regression/xsl_reports/xsl/v2/add_expected_results.xsl"  
> "/
> sierra/Src/kbelco/boost/reporting/trunk/incoming/trunk/processed/
> Debian-Sid-trimmed.xml"
>
>                         Unknown test type "run_mpi"
>
> Any ideas?

Okay, looks like someone added support for running / reporting MPI,  
but didn't update all the files used by the report processing.  Not  
sure who updated this but either we should revert the change, as trunk  
tests haven't run since Wednesday (and remove the Debian-Sid results),  
or fix this issue.  I won't be able to look at it until Sunday evening  
at the earliest.

It seems like these files are missing references to run_mpi.

./regression/xsl_reports/test/generate_test_results.py:    types =  
[ "compile", "compile_fail", "link", "link_fail", "run", "run_fail",  
"run_pyd" ]
./regression/xsl_reports/xsl/v2/
add_expected_results.xsl:                <xsl:when test="$type='run'  
or $type='run_fail' or $type='run_pyd'">
./regression/xsl_reports/xsl/v2/result_page.xsl:            <xsl:when  
test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
./regression/xsl_reports/xsl/result_page.xsl:            <xsl:when  
test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
./regression/xsl_reports/test_results.xsd:            <xs:enumeration  
value="run_fail"/>

Because I don't update the Boost installation in the test reporting  
directory, if someone fixes this problem, please let me know so I can  
update.  Trunk testing will remain broken until we revert or fix this  
issue, sorry.

-- Noel


_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[smr99]

On Sat, Aug 08, 2009 at 02:05:09PM -0600, Belcourt, Kenneth wrote:
>
> On Aug 8, 2009, at 1:52 PM, Belcourt, Kenneth wrote:
>
> >                        Unknown test type "run_mpi"
> >
> >Any ideas?

In my view, it would be a good thing to actually test the MPI libraries.
No-one has been doing so thus far.

Could you comment on http://lists.boost.org/boost-testing/2009/08/6355.php

Thanks,
-Steve



_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[Vladimir Prus-3]

Belcourt, Kenneth wrote:

> It seems like these files are missing references to run_mpi.
>
> ./regression/xsl_reports/test/generate_test_results.py:    types =
> [ "compile", "compile_fail", "link", "link_fail", "run", "run_fail",
> "run_pyd" ]
> ./regression/xsl_reports/xsl/v2/
> add_expected_results.xsl:                <xsl:when test="$type='run'
> or $type='run_fail' or $type='run_pyd'">
> ./regression/xsl_reports/xsl/v2/result_page.xsl:            <xsl:when
> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
> ./regression/xsl_reports/xsl/result_page.xsl:            <xsl:when
> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
> ./regression/xsl_reports/test_results.xsd:            <xs:enumeration
> value="run_fail"/>
>
> Because I don't update the Boost installation in the test reporting
> directory, if someone fixes this problem, please let me know so I can
> update.  Trunk testing will remain broken until we revert or fix this
> issue, sorry.

I have fixed this issue, on trunk, after testing that result generation
locally appears to work right.

Let me know if this should be merged to release branch.

- Volodya


_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[Beman Dawes]

On Mon, Aug 10, 2009 at 6:22 AM, Vladimir Prus<vladimir@...> wrote:

> Belcourt, Kenneth wrote:
>
>> It seems like these files are missing references to run_mpi.
>>
>> ./regression/xsl_reports/test/generate_test_results.py:    types =
>> [ "compile", "compile_fail", "link", "link_fail", "run", "run_fail",
>> "run_pyd" ]
>> ./regression/xsl_reports/xsl/v2/
>> add_expected_results.xsl:                <xsl:when test="$type='run'
>> or $type='run_fail' or $type='run_pyd'">
>> ./regression/xsl_reports/xsl/v2/result_page.xsl:            <xsl:when
>> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
>> ./regression/xsl_reports/xsl/result_page.xsl:            <xsl:when
>> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
>> ./regression/xsl_reports/test_results.xsd:            <xs:enumeration
>> value="run_fail"/>
>>
>> Because I don't update the Boost installation in the test reporting
>> directory, if someone fixes this problem, please let me know so I can
>> update.  Trunk testing will remain broken until we revert or fix this
>> issue, sorry.
>
> I have fixed this issue, on trunk, after testing that result generation
> locally appears to work right.

Thanks, Volodya!

> Let me know if this should be merged to release branch.

AFAICS, tests are cycling normally for the release branch. Thus I'd
prefer to hold off the merge until after 1.40.0 ships.

--Beman
_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[Vladimir Prus-3]

Beman Dawes wrote:

> On Mon, Aug 10, 2009 at 6:22 AM, Vladimir Prus<vladimir@...> wrote:
>> Belcourt, Kenneth wrote:
>>
>>> It seems like these files are missing references to run_mpi.
>>>
>>> ./regression/xsl_reports/test/generate_test_results.py:    types =
>>> [ "compile", "compile_fail", "link", "link_fail", "run", "run_fail",
>>> "run_pyd" ]
>>> ./regression/xsl_reports/xsl/v2/
>>> add_expected_results.xsl:                <xsl:when test="$type='run'
>>> or $type='run_fail' or $type='run_pyd'">
>>> ./regression/xsl_reports/xsl/v2/result_page.xsl:            <xsl:when
>>> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
>>> ./regression/xsl_reports/xsl/result_page.xsl:            <xsl:when
>>> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
>>> ./regression/xsl_reports/test_results.xsd:            <xs:enumeration
>>> value="run_fail"/>
>>>
>>> Because I don't update the Boost installation in the test reporting
>>> directory, if someone fixes this problem, please let me know so I can
>>> update.  Trunk testing will remain broken until we revert or fix this
>>> issue, sorry.
>>
>> I have fixed this issue, on trunk, after testing that result generation
>> locally appears to work right.
>
> Thanks, Volodya!
>
>> Let me know if this should be merged to release branch.
>
> AFAICS, tests are cycling normally for the release branch.

For avoidance of doubt:

1. Release testing does not show MPI at all, since no tester is configured
so.
2. MPI test results don't show up on trunk yet, either. IIUC, Noel
needs to update from trunk explicitly.

> Thus I'd
> prefer to hold off the merge until after 1.40.0 ships.

OK.

- Volodya


_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[K. Noel Belcourt]

Hi Volodya,

On Aug 10, 2009, at 4:22 AM, Vladimir Prus wrote:

> Belcourt, Kenneth wrote:
>
>> It seems like these files are missing references to run_mpi.
>>
>> ./regression/xsl_reports/test/generate_test_results.py:    types =
>> [ "compile", "compile_fail", "link", "link_fail", "run", "run_fail",
>> "run_pyd" ]
>> ./regression/xsl_reports/xsl/v2/
>> add_expected_results.xsl:                <xsl:when test="$type='run'
>> or $type='run_fail' or $type='run_pyd'">
>> ./regression/xsl_reports/xsl/v2/result_page.xsl:            <xsl:when
>> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
>> ./regression/xsl_reports/xsl/result_page.xsl:            <xsl:when
>> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
>> ./regression/xsl_reports/test_results.xsd:            <xs:enumeration
>> value="run_fail"/>
>>
>> Because I don't update the Boost installation in the test reporting
>> directory, if someone fixes this problem, please let me know so I can
>> update.  Trunk testing will remain broken until we revert or fix this
>> issue, sorry.
>
> I have fixed this issue, on trunk, after testing that result  
> generation
> locally appears to work right.

Okay, I too fixed it last evening in the project where I run the  
reporting.  It seemed to be working fine, though I didn't commit the  
changes to the repository.  I do notice, however, that this morning  
many of the trunk testers have been deleted?  Was that you or is  
there something wrong with the reporting?

Here's all that remain.

Writing runner document Huang-Vista-x64-intel
Writing runner document Huang-Vista-x64
Writing runner document Huang-Vista-x86_32
Writing runner document Huang-Vista-x86_32_intel
Writing runner document IBM_Canada_Ltd
Writing runner document RWVC10
Writing runner document RW_Mingw
Writing runner document RW_WinXP_VC
Writing runner document Sandia-gcc-64
Writing runner document Sandia-intel-10.0
Writing runner document Sandia-leopard-x86
Writing runner document Sandia-pathscale
Writing runner document Sandia-tiger-x86

Any ideas?

-- Noel

>
> Let me know if this should be merged to release branch.
>
> - Volodya
>
>
> _______________________________________________
> Boost-Testing mailing list
> Boost-Testing@...
> http://lists.boost.org/mailman/listinfo.cgi/boost-testing
>

_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[Vladimir Prus-3]

K. Noel Belcourt wrote:

> Hi Volodya,
>
> On Aug 10, 2009, at 4:22 AM, Vladimir Prus wrote:
>
>> Belcourt, Kenneth wrote:
>>
>>> It seems like these files are missing references to run_mpi.
>>>
>>> ./regression/xsl_reports/test/generate_test_results.py:    types =
>>> [ "compile", "compile_fail", "link", "link_fail", "run", "run_fail",
>>> "run_pyd" ]
>>> ./regression/xsl_reports/xsl/v2/
>>> add_expected_results.xsl:                <xsl:when test="$type='run'
>>> or $type='run_fail' or $type='run_pyd'">
>>> ./regression/xsl_reports/xsl/v2/result_page.xsl:            <xsl:when
>>> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
>>> ./regression/xsl_reports/xsl/result_page.xsl:            <xsl:when
>>> test="$test_type='run_fail'">     <xsl:text>rf</xsl:text> </xsl:when>
>>> ./regression/xsl_reports/test_results.xsd:            <xs:enumeration
>>> value="run_fail"/>
>>>
>>> Because I don't update the Boost installation in the test reporting
>>> directory, if someone fixes this problem, please let me know so I can
>>> update.  Trunk testing will remain broken until we revert or fix this
>>> issue, sorry.
>>
>> I have fixed this issue, on trunk, after testing that result
>> generation
>> locally appears to work right.
>
> Okay, I too fixed it last evening in the project where I run the
> reporting.  It seemed to be working fine, though I didn't commit the
> changes to the repository.  I do notice, however, that this morning
> many of the trunk testers have been deleted?  Was that you or is
> there something wrong with the reporting?
>
> Here's all that remain.
>
> Writing runner document Huang-Vista-x64-intel
> Writing runner document Huang-Vista-x64
> Writing runner document Huang-Vista-x86_32
> Writing runner document Huang-Vista-x86_32_intel
> Writing runner document IBM_Canada_Ltd
> Writing runner document RWVC10
> Writing runner document RW_Mingw
> Writing runner document RW_WinXP_VC
> Writing runner document Sandia-gcc-64
> Writing runner document Sandia-intel-10.0
> Writing runner document Sandia-leopard-x86
> Writing runner document Sandia-pathscale
> Writing runner document Sandia-tiger-x86

I did not delete any test results. Debian-Sid test results appear
to be available on the ftp  server, too, and are fetched by the
processing script. Can you let me know the complete command you
use to process the results and upload them?

- Volodya


_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[K. Noel Belcourt]

On Aug 10, 2009, at 11:15 AM, Vladimir Prus wrote:

> K. Noel Belcourt wrote:
>
>> Hi Volodya,
>>
>> On Aug 10, 2009, at 4:22 AM, Vladimir Prus wrote:
>>
>>> I have fixed this issue, on trunk, after testing that result
>>> generation
>>> locally appears to work right.
>>
>> Okay, I too fixed it last evening in the project where I run the
>> reporting.  It seemed to be working fine, though I didn't commit the
>> changes to the repository.  I do notice, however, that this morning
>> many of the trunk testers have been deleted?  Was that you or is
>> there something wrong with the reporting?

This is my mistake.  I still had a conflict following the update.  
The next reporting cycle should look better.

Thanks.

-- Noel


_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing

[smr99]

On Mon, Aug 10, 2009 at 10:15:06AM -0400, Beman Dawes wrote:
> On Mon, Aug 10, 2009 at 6:22 AM, Vladimir Prus<vladimir@...> wrote:

> > I have fixed this issue, on trunk, after testing that result generation
> > locally appears to work right.
>
> Thanks, Volodya!
>
> > Let me know if this should be merged to release branch.
>
> AFAICS, tests are cycling normally for the release branch. Thus I'd
> prefer to hold off the merge until after 1.40.0 ships.

I don't think the tests are cycling normally.  I have MPI enabled in
release as well as trunk but the MPI results were being dropped.

-Steve


_______________________________________________
Boost-Testing mailing list
Boost-Testing@...
http://lists.boost.org/mailman/listinfo.cgi/boost-testing