serialization:question regarding test
It seems I've succeeded in getting my serialization project checked in. (I've held back the Jamfile in the test directory pending a tiny tweak) And I have a couple of questions regarding testing. a) in order for libraries to be built for Borland and VC 6.0 which don't support Spirit 1.8 but do support spirit 1.6, the Jamfile checks for the environmental variable SPIRIT_ROOT and if found presumes it contains the root of the directory where Spirit 1.6 is located. This has worked well in my local environment. An environment which tests this library for these compilers will also need to have Spirit 1.6 installed and have the SPIRIT_ROOT variable set accordingly. I don't know who I should inform about this. b) its unclear to me how to exclude certain platforms. I've been unable go get non-intrusive serialization with Commeau - much to my disappointement. This is pretty much a show-stopper for this compiler. (Other than this it seems to compile cleanly - though perhaps a tad picky with warnings). So I would like to know how to exclude Comeau from the tests. c) As currently loaded, the test programs create temporary files in the systems temporary directory. And leaves them there - I occasionally delete them in masse. It only just dawned on me that this would be very inconvenient for the test setup so I'm going to tweak the tests to remove their trash at the end. So in some case some trash may be left over but shouldn't accumulate at a large rate as before. I hope this is acceptable. Robert Ramey
"Robert Ramey" <ramey@rrsd.com> writes:
It seems I've succeeded in getting my serialization project checked in.
(I've held back the Jamfile in the test directory pending a tiny tweak)
And I have a couple of questions regarding testing.
a) in order for libraries to be built for Borland and VC 6.0 which don't support Spirit 1.8 but do support spirit 1.6, the Jamfile checks for the environmental variable SPIRIT_ROOT and if found presumes it contains the root of the directory where Spirit 1.6 is located. This has worked well in my local environment. An environment which tests this library for these compilers will also need to have Spirit 1.6 installed and have the SPIRIT_ROOT variable set accordingly. I don't know who I should inform about this.
That's not going to work well in the Boost regression suite. Tests get run against a current copy of the Boost tree, and we don't have any provision to check out (say) an old branch of Spirit. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com
David Abrahams wrote:
"Robert Ramey" <ramey@rrsd.com> writes:
It seems I've succeeded in getting my serialization project checked in.
(I've held back the Jamfile in the test directory pending a tiny tweak)
And I have a couple of questions regarding testing.
a) in order for libraries to be built for Borland and VC 6.0 which don't support Spirit 1.8 but do support spirit 1.6, the Jamfile checks for the environmental variable SPIRIT_ROOT and if found presumes it contains the root of the directory where Spirit 1.6 is located. This has worked well in my local environment. An environment which tests this library for these compilers will also need to have Spirit 1.6 installed and have the SPIRIT_ROOT variable set accordingly. I don't know who I should inform about this.
That's not going to work well in the Boost regression suite. Tests get run against a current copy of the Boost tree, and we don't have any provision to check out (say) an old branch of Spirit.
I sympathize with Robert and I wish I can find a way to help him. Unfortunately, I can't think of another way other than re-merging the 1.6.x branch with 1.8.x which is not possible at this point in time. The only suggestion I can make is add a note in the regression result page explaining the situation. Alexey added a note to Spirit's result page, for example: see http://tinyurl.com/6ev67. Regards, -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
Robert Ramey writes:
It seems I've succeeded in getting my serialization project checked in.
Excellent!
(I've held back the Jamfile in the test directory pending a tiny tweak)
And I have a couple of questions regarding testing.
a) in order for libraries to be built for Borland and VC 6.0 which don't support Spirit 1.8 but do support spirit 1.6, the Jamfile checks for the environmental variable SPIRIT_ROOT and if found presumes it contains the root of the directory where Spirit 1.6 is located. This has worked well in my local environment. An environment which tests this library for these compilers will also need to have Spirit 1.6 installed and have the SPIRIT_ROOT variable set accordingly. I don't know who I should inform about this.
Theoretically, it would be possible to arrange (at least for us here at Meta), but I'm afraid we don't have time for this. I'd suggest you to mark the library as unusable on VC 6.0 with a comment explaining the situation in detail.
b) its unclear to me how to exclude certain platforms. I've been unable go get non-intrusive serialization with Commeau - much to my disappointement. This is pretty much a show-stopper for this compiler. (Other than this it seems to compile cleanly - though perhaps a tad picky with warnings). So I would like to know how to exclude Comeau from the tests.
Please see the existing '<mark-unusable>' sections in "boost/status/explicit-failures-markup.xml" (http://tinyurl.com/2gbvr).
c) As currently loaded, the test programs create temporary files in the systems temporary directory. And leaves them there - I occasionally delete them in masse. It only just dawned on me that this would be very inconvenient for the test setup so I'm going to tweak the tests to remove their trash at the end. So in some case some trash may be left over but shouldn't accumulate at a large rate as before. I hope this is acceptable.
Sounds fine. -- Aleksey Gurtovoy MetaCommunications Engineering
Aleksey Gurtovoy wrote:
Robert Ramey writes:
a) in order for libraries to be built for Borland and VC 6.0 which don't support Spirit 1.8 but do support spirit 1.6, the Jamfile checks for the environmental variable SPIRIT_ROOT and if found presumes it contains the root of the directory where Spirit 1.6 is located. This has worked well in my local environment. An environment which tests this library for these compilers will also need to have Spirit 1.6 installed and have the SPIRIT_ROOT variable set accordingly. I don't know who I should inform about this.
Theoretically, it would be possible to arrange (at least for us here at Meta), but I'm afraid we don't have time for this. I'd suggest you to mark the library as unusable on VC 6.0 with a comment explaining the situation in detail.
Hi Aleksey, I'd appreciate this a lot if we could do this sometime in the future. Would it also be possible to have Spirit 1.6.x take part in the daily regressions? It would be nice if I could check in Spirit 1.6.x in a separate directory. This will ensure that the version will remain compatible with current and future boost versions. I'm afraid Spirit 1.6.x will still be with us for a long time. Tell me if this is like asking for the moon :-P Thanks! -- Joel de Guzman http://www.boost-consulting.com http://spirit.sf.net
Joel de Guzman writes:
Aleksey Gurtovoy wrote:
Robert Ramey writes:
a) in order for libraries to be built for Borland and VC 6.0 which don't support Spirit 1.8 but do support spirit 1.6, the Jamfile checks for the environmental variable SPIRIT_ROOT and if found presumes it contains the root of the directory where Spirit 1.6 is located. This has worked well in my local environment. An environment which tests this library for these compilers will also need to have Spirit 1.6 installed and have the SPIRIT_ROOT variable set accordingly. I don't know who I should inform about this. Theoretically, it would be possible to arrange (at least for us here at Meta), but I'm afraid we don't have time for this. I'd suggest you to mark the library as unusable on VC 6.0 with a comment explaining the situation in detail.
Hi Aleksey,
Hi Joel,
I'd appreciate this a lot if we could do this sometime in the future. Would it also be possible to have Spirit 1.6.x take part in the daily regressions?
Against the current CVS? I think we can afford it; may be not daily, though.
It would be nice if I could check in Spirit 1.6.x in a separate directory. This will ensure that the version will remain compatible with current and future boost versions. I'm afraid Spirit 1.6.x will still be with us for a long time.
Let's return to this when the release is out. -- Aleksey Gurtovoy MetaCommunications Engineering
participants (4)
-
Aleksey Gurtovoy -
David Abrahams -
Joel de Guzman -
Robert Ramey