(sorry, dropped the cc by mistake) David Abrahams wrote:

Okay, here are some issues I think ought to be solved, in no particular order, some (much) more important than others:

[...] * No way for a test to fail with a "skipped" status (gray box). This is similar to

* no mechanism for communicating that tests are known not to work on some platform (toolset+os) to the build system, and so avoid building them

but it can rely on Boost.Config macros, which may not be easily accessible to the build system.

on Fri May 04 2007, "Gennadiy Rozental" wrote:

"David Abrahams" wrote in message news:876478d51y.fsf@valverde.peloton...

...

* No way for a developer to request testing results for a specific branch

And against particular branch.

How is "for a specific branch" different from "against a particular branch?" it seems as though you're repeating what I meant to say (?)

That's what independent versioning should address.

I don't see a relationship between the two issues. The ability to request test results against a specific branch has obvious utility; you can try out changes and see how portable they are without disturbing general test results. Independent versioning, by it self, does not address that need. You'd still need to implement all the same testing infrastructure, so I don't see the relevance here. -- Dave Abrahams Boost Consulting www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com

on Sat May 05 2007, "Gennadiy Rozental" wrote:

"David Abrahams" wrote in message news:87zm4k87rw.fsf@valverde.peloton...

...

on Fri May 04 2007, "Gennadiy Rozental" wrote:

...

"David Abrahams" wrote in message news:876478d51y.fsf@valverde.peloton...

...

* No way for a developer to request testing results for a specific branch

And against particular branch.

How is "for a specific branch" different from "against a particular branch?" it seems as though you're repeating what I meant to say (?)

My library depend in lib A, B, C. I want to test against new_dev branch of A, HEAD branch of B and 1_33 branch of C.

So assemble a branch that contains everything you want, check it in, and request the test. SVN is really good for that sort of thing because of the way it copies "by reference".

...

...

That's what independent versioning should address.

I don't see a relationship between the two issues. The ability to request test results against a specific branch has obvious utility; you can try out changes and see how portable they are without disturbing general test results. Independent versioning, by it self, does not address that need. You'd still need to implement all the same testing infrastructure, so I don't see the relevance here.

Yes. independent versioning has little to do with "testing for a specific branch". But has everything to do with "testing against particular branch" ;)

I still don't see it, sorry. -- Dave Abrahams Boost Consulting www.boost-consulting.com Don't Miss BoostCon 2007! ==> http://www.boostcon.com

on Sun May 06 2007, "Gennadiy Rozental" wrote:

"David Abrahams" wrote in message news:87tzur78cq.fsf@valverde.peloton...

...

on Sat May 05 2007, "Gennadiy Rozental" wrote:

...

My library depend in lib A, B, C. I want to test against new_dev branch of A, HEAD branch of B and 1_33 branch of C.

So assemble a branch that contains everything you want, check it in, and request the test. SVN is really good for that sort of thing because of the way it copies "by reference".

Does it means that my branch will keep track of changes made in referenced branches? If not it's useless in practice.

You could do that with svn:externals.