How does V2 testing work without a Jamfile.v2?
The regression tests for Lambda seem up and running, but I see no Jamfile.v2 in libs/lambda/test. There is a Jamfile but it appears to be v1 and is apparently not being used by the testers; I've added two new tests to it and they did not appear in the table. How does v2 testing work? Magic? Local v2 patches not reflected in HEAD even though HEAD is being tested?
Peter Dimov wrote:
The regression tests for Lambda seem up and running, but I see no Jamfile.v2 in libs/lambda/test. There is a Jamfile
I don't even see a Jamfile.
but it appears to be v1 and is apparently not being used by the testers; I've added two new tests to it and they did not appear in the table.
How does v2 testing work? Magic? Local v2 patches not reflected in HEAD even though HEAD is being tested?
Take a look at status/Jamfile.v2: test-suite lambda : [ run libs/lambda/test/algorithm_test.cpp test_exec_monitor ] [ run libs/lambda/test/bind_tests_simple.cpp test_exec_monitor ] [ run libs/lambda/test/bind_tests_advanced.cpp test_exec_monitor ] [ run libs/lambda/test/bind_tests_simple_f_refs.cpp test_exec_monitor ] [ run libs/lambda/test/bll_and_function.cpp test_exec_monitor ] This (declaring tests in status/Jamfile*) is not the best practice, however that's how lambda tests were declared in V1. It was carried over to V2. - Volodya
Vladimir Prus wrote:
Peter Dimov wrote:
The regression tests for Lambda seem up and running, but I see no Jamfile.v2 in libs/lambda/test. There is a Jamfile
I don't even see a Jamfile.
http://boost.cvs.sourceforge.net/boost/boost/libs/lambda/test/Jamfile?view=l... You're probably looking at the RC_1_34 branch.
How does v2 testing work? Magic? Local v2 patches not reflected in HEAD even though HEAD is being tested?
Take a look at status/Jamfile.v2:
test-suite lambda : [ run libs/lambda/test/algorithm_test.cpp test_exec_monitor ]
... Aha. Thanks. This is evil, right? :-)
Peter Dimov wrote:
Vladimir Prus wrote:
Peter Dimov wrote:
The regression tests for Lambda seem up and running, but I see no Jamfile.v2 in libs/lambda/test. There is a Jamfile
I don't even see a Jamfile.
http://boost.cvs.sourceforge.net/boost/boost/libs/lambda/test/Jamfile?view=l...
You're probably looking at the RC_1_34 branch.
Ehm, so we still have V1 Jamfiles on HEAD? Weird, we probably should remove them.
How does v2 testing work? Magic? Local v2 patches not reflected in HEAD even though HEAD is being tested?
Take a look at status/Jamfile.v2:
test-suite lambda : [ run libs/lambda/test/algorithm_test.cpp test_exec_monitor ]
...
Aha. Thanks. This is evil, right? :-)
Yes. But it's up to lambda maintainers to fix ;-) - Volodya
Peter Dimov wrote:
The regression tests for Lambda seem up and running, but I see no Jamfile.v2 in libs/lambda/test. There is a Jamfile but it appears to be v1 and is apparently not being used by the testers; I've added two new tests to it and they did not appear in the table.
How does v2 testing work? Magic? Local v2 patches not reflected in HEAD even though HEAD is being tested?
There's a lambda test-suite in the status/Jamfile.v2 file. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
participants (3)
-
Peter Dimov -
Rene Rivera -
Vladimir Prus