[modular] and status/explicit-failures-markup.xml
Dear modularists, I've just tried to make changes to modular-boost/status/explicit-failures-markup.xml. Since I have only write permission to my own library libs/icl in modular boost, trying to push my changes failed. What is the right way to change the regression test markups in modular-boost? Best, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de
AMDG On 02/01/2014 11:03 AM, Joachim Faulhaber wrote:
Dear modularists,
I've just tried to make changes to modular-boost/status/explicit-failures-markup.xml.
Since I have only write permission to my own library libs/icl in modular boost, trying to push my changes failed.
What is the right way to change the regression test markups in modular-boost?
This hasn't been dealt with at all, yet. What we ought to do is to let each library have its own markup file. It shouldn't be too difficult to load multiple files in the report generator. In Christ, Steven Watanabe
2014-02-01 Steven Watanabe
AMDG
On 02/01/2014 11:03 AM, Joachim Faulhaber wrote:
Dear modularists,
I've just tried to make changes to modular-boost/status/explicit-failures-markup.xml.
Since I have only write permission to my own library libs/icl in modular boost, trying to push my changes failed.
What is the right way to change the regression test markups in modular-boost?
This hasn't been dealt with at all, yet. What we ought to do is to let each library have its own markup file. It shouldn't be too difficult to load multiple files in the report generator.
thanks for the information... could someone then just insert after line 2127: <toolset name="msvc-11.0*"/> a new line <toolset name="msvc-12.0*"/> both for develop and master that would make my test results more greenish, since there is an expected compiler bug for msvc-12.0. Thanks in advance, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de
On 1 February 2014 19:43, Joachim Faulhaber
This hasn't been dealt with at all, yet. What we ought to do is to let each library have its own markup file. It shouldn't be too difficult to load multiple files in the report generator.
I want to do something similar for generating the library list on the website. Perhaps we should have a standard location for such things? Maybe a 'meta' directory in each module? The other thing we can do is have a separate module. I'd rather have one for boost-specific build files in general, which would need a bit of reorganisation.
thanks for the information...
could someone then just insert after line 2127: <toolset name="msvc-11.0*"/> a new line <toolset name="msvc-12.0*"/>
both for develop and master
I just did it. But you can create a pull request, you can do it through github - go to the source file and click 'edit'.
2014-02-01 Daniel James
On 1 February 2014 19:43, Joachim Faulhaber
wrote: This hasn't been dealt with at all, yet. What we ought to do is to let each library have its own markup file. It shouldn't be too difficult to load multiple files in the report generator.
I want to do something similar for generating the library list on the website. Perhaps we should have a standard location for such things? Maybe a 'meta' directory in each module?
The other thing we can do is have a separate module. I'd rather have one for boost-specific build files in general, which would need a bit of reorganisation.
thanks for the information...
could someone then just insert after line 2127: <toolset name="msvc-11.0*"/> a new line <toolset name="msvc-12.0*"/>
both for develop and master
I just did it.
Thanks a lot
But you can create a pull request, you can do it through github - go to the source file and click 'edit'.
Ok, I'll do this on the next occasion. Cheers, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de
participants (3)
-
Daniel James
-
Joachim Faulhaber
-
Steven Watanabe