Adding regression tests for mingw(-64)/gcc and clang on Windows

classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

Adding regression tests for mingw(-64)/gcc and clang on Windows

Edward Diener-3
For a long time now we have had no regression tests for mingw/gcc or
clang targeting gcc on Windows. The only regression tests for Windows
are for various releases of VC++.

I have limited resources but I have a laptop usually sitting idle,
except for occasional travel where I take it with me, and I am set up to
run tests on that machine for mingw/gcc and clang on Windows.

However mingw/gcc and clang have limitations when running tests in that,
both relying on various mingw/gcc implementations, the path to the
implementation must be added at the beginning of the PATH before running
any of the tests. I have already argued with the mingw-64 people about
this necessity but they are adamant that this should be the case even
just to compile/link properly ( and have setup their directory structure
to enforce it ), and I don't want to waste my breath further with them.

Currently I have a batch file that does that for me when running tests
for any particular library, but I don't know how that can be achieved
when running the regression tests unless possibly I run regression tests
for only a single toolset at a time, and manipulate the PATH accodingly.
But that is really time consuming since evidently all of Boost must be
downloaded to the run directory each time. Is there an easy solution to
this or do I have to look at run.py and try modify it accordingly ( I
know Python well ) ?

Also I notice on the Boost web site regression test page (
http://www.boost.org/development/running_regression_tests.html ) that
the options of the regression tests are somewhat documented but none of
the commands are documented. Is there further documentation about the
regression test commands anywhere ?

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Edward Diener-3
On 8/11/2015 4:38 PM, Edward Diener wrote:

> For a long time now we have had no regression tests for mingw/gcc or
> clang targeting gcc on Windows. The only regression tests for Windows
> are for various releases of VC++.
>
> I have limited resources but I have a laptop usually sitting idle,
> except for occasional travel where I take it with me, and I am set up to
> run tests on that machine for mingw/gcc and clang on Windows.
>
> However mingw/gcc and clang have limitations when running tests in that,
> both relying on various mingw/gcc implementations, the path to the
> implementation must be added at the beginning of the PATH before running
> any of the tests. I have already argued with the mingw-64 people about
> this necessity but they are adamant that this should be the case even
> just to compile/link properly ( and have setup their directory structure
> to enforce it ), and I don't want to waste my breath further with them.
>
> Currently I have a batch file that does that for me when running tests
> for any particular library, but I don't know how that can be achieved
> when running the regression tests unless possibly I run regression tests
> for only a single toolset at a time, and manipulate the PATH accodingly.
> But that is really time consuming since evidently all of Boost must be
> downloaded to the run directory each time. Is there an easy solution to
> this or do I have to look at run.py and try modify it accordingly ( I
> know Python well ) ?

I figured out what my problem was running multiple tests, and how to
achieve regression testing with clang and gcc on Windows.

>
> Also I notice on the Boost web site regression test page (
> http://www.boost.org/development/running_regression_tests.html ) that
> the options of the regression tests are somewhat documented but none of
> the commands are documented. Is there further documentation about the
> regression test commands anywhere ?

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Tom Kent
Can you document it somewhere? I'd be interested in adding clang/gcc on mingw runs to the ones I do on windows, but I had never had much luck getting them up and running.

Tom

On Tue, Aug 11, 2015 at 7:20 PM, Edward Diener <[hidden email]> wrote:
On 8/11/2015 4:38 PM, Edward Diener wrote:
For a long time now we have had no regression tests for mingw/gcc or
clang targeting gcc on Windows. The only regression tests for Windows
are for various releases of VC++.

I have limited resources but I have a laptop usually sitting idle,
except for occasional travel where I take it with me, and I am set up to
run tests on that machine for mingw/gcc and clang on Windows.

However mingw/gcc and clang have limitations when running tests in that,
both relying on various mingw/gcc implementations, the path to the
implementation must be added at the beginning of the PATH before running
any of the tests. I have already argued with the mingw-64 people about
this necessity but they are adamant that this should be the case even
just to compile/link properly ( and have setup their directory structure
to enforce it ), and I don't want to waste my breath further with them.

Currently I have a batch file that does that for me when running tests
for any particular library, but I don't know how that can be achieved
when running the regression tests unless possibly I run regression tests
for only a single toolset at a time, and manipulate the PATH accodingly.
But that is really time consuming since evidently all of Boost must be
downloaded to the run directory each time. Is there an easy solution to
this or do I have to look at run.py and try modify it accordingly ( I
know Python well ) ?

I figured out what my problem was running multiple tests, and how to achieve regression testing with clang and gcc on Windows.



Also I notice on the Boost web site regression test page (
http://www.boost.org/development/running_regression_tests.html ) that
the options of the regression tests are somewhat documented but none of
the commands are documented. Is there further documentation about the
regression test commands anywhere ?

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing


_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Edward Diener-3
On 8/11/2015 9:40 PM, Tom Kent wrote:
> Can you document it somewhere? I'd be interested in adding clang/gcc on
> mingw runs to the ones I do on windows, but I had never had much luck
> getting them up and running.

I thought I had figured it out but it is still not working when trying
to run the regression tests. I am getting messages as if the particular
version of mingw-64/gcc used in a regression test is not in my path when
some executable is being run or tested ( so and so mingw-64/gcc DLL can
not be found ).

Yet when I manually test out libraries in the latest boost trunk
everything is fine. I can see when I run tests that Boost build is
prepending the path to the mingw-64/gcc version I am using to the
Windows PATH so that when the test is run, everything is found.

Soemhow the regression tests are not doing the same thing in running the
tests that I do manually to test any particular library. I will be
trying to find out what that is.

>
> Tom
>
> On Tue, Aug 11, 2015 at 7:20 PM, Edward Diener <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     On 8/11/2015 4:38 PM, Edward Diener wrote:
>
>         For a long time now we have had no regression tests for mingw/gcc or
>         clang targeting gcc on Windows. The only regression tests for
>         Windows
>         are for various releases of VC++.
>
>         I have limited resources but I have a laptop usually sitting idle,
>         except for occasional travel where I take it with me, and I am
>         set up to
>         run tests on that machine for mingw/gcc and clang on Windows.
>
>         However mingw/gcc and clang have limitations when running tests
>         in that,
>         both relying on various mingw/gcc implementations, the path to the
>         implementation must be added at the beginning of the PATH before
>         running
>         any of the tests. I have already argued with the mingw-64 people
>         about
>         this necessity but they are adamant that this should be the case
>         even
>         just to compile/link properly ( and have setup their directory
>         structure
>         to enforce it ), and I don't want to waste my breath further
>         with them.
>
>         Currently I have a batch file that does that for me when running
>         tests
>         for any particular library, but I don't know how that can be
>         achieved
>         when running the regression tests unless possibly I run
>         regression tests
>         for only a single toolset at a time, and manipulate the PATH
>         accodingly.
>         But that is really time consuming since evidently all of Boost
>         must be
>         downloaded to the run directory each time. Is there an easy
>         solution to
>         this or do I have to look at run.py and try modify it
>         accordingly ( I
>         know Python well ) ?
>
>
>     I figured out what my problem was running multiple tests, and how to
>     achieve regression testing with clang and gcc on Windows.
>
>
>
>         Also I notice on the Boost web site regression test page (
>         http://www.boost.org/development/running_regression_tests.html )
>         that
>         the options of the regression tests are somewhat documented but
>         none of
>         the commands are documented. Is there further documentation
>         about the
>         regression test commands anywhere ?

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Jim Bell


On 2015-08-11 11:47 PM, Edward Diener wrote:

> On 8/11/2015 9:40 PM, Tom Kent wrote:
>> Can you document it somewhere? I'd be interested in adding clang/gcc on
>> mingw runs to the ones I do on windows, but I had never had much luck
>> getting them up and running.
>
> I thought I had figured it out but it is still not working when trying
> to run the regression tests. I am getting messages as if the
> particular version of mingw-64/gcc used in a regression test is not in
> my path when some executable is being run or tested ( so and so
> mingw-64/gcc DLL can not be found ).
>
> Yet when I manually test out libraries in the latest boost trunk
> everything is fine. I can see when I run tests that Boost build is
> prepending the path to the mingw-64/gcc version I am using to the
> Windows PATH so that when the test is run, everything is found.

I have mingw tests for mingw-32, mingw-w64 gcc 4.9, 4.8, 4.7, 4.6, 4.5,
and 4.4.  Also the mingw-gcc that ships with Qt 5.4, Qt 5.2 and Qt 4.

I don't recall everything I did to get it working, but I'll fire one
back up tomorrow.

As I recall, clang wouldn't build one kind of library (dynamic or
static, I don't recall which), and that killed the results.  Has that
changed?


>
> Soemhow the regression tests are not doing the same thing in running
> the tests that I do manually to test any particular library. I will be
> trying to find out what that is.
>
>>
>> Tom
>>
>> On Tue, Aug 11, 2015 at 7:20 PM, Edward Diener <[hidden email]
>> <mailto:[hidden email]>> wrote:
>>
>>     On 8/11/2015 4:38 PM, Edward Diener wrote:
>>
>>         For a long time now we have had no regression tests for
>> mingw/gcc or
>>         clang targeting gcc on Windows. The only regression tests for
>>         Windows
>>         are for various releases of VC++.
>>
>>         I have limited resources but I have a laptop usually sitting
>> idle,
>>         except for occasional travel where I take it with me, and I am
>>         set up to
>>         run tests on that machine for mingw/gcc and clang on Windows.
>>
>>         However mingw/gcc and clang have limitations when running tests
>>         in that,
>>         both relying on various mingw/gcc implementations, the path
>> to the
>>         implementation must be added at the beginning of the PATH before
>>         running
>>         any of the tests. I have already argued with the mingw-64 people
>>         about
>>         this necessity but they are adamant that this should be the case
>>         even
>>         just to compile/link properly ( and have setup their directory
>>         structure
>>         to enforce it ), and I don't want to waste my breath further
>>         with them.
>>
>>         Currently I have a batch file that does that for me when running
>>         tests
>>         for any particular library, but I don't know how that can be
>>         achieved
>>         when running the regression tests unless possibly I run
>>         regression tests
>>         for only a single toolset at a time, and manipulate the PATH
>>         accodingly.
>>         But that is really time consuming since evidently all of Boost
>>         must be
>>         downloaded to the run directory each time. Is there an easy
>>         solution to
>>         this or do I have to look at run.py and try modify it
>>         accordingly ( I
>>         know Python well ) ?
>>
>>
>>     I figured out what my problem was running multiple tests, and how to
>>     achieve regression testing with clang and gcc on Windows.
>>
>>
>>
>>         Also I notice on the Boost web site regression test page (
>> http://www.boost.org/development/running_regression_tests.html )
>>         that
>>         the options of the regression tests are somewhat documented but
>>         none of
>>         the commands are documented. Is there further documentation
>>         about the
>>         regression test commands anywhere ?
>
>

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Edward Diener-3
On 8/12/2015 11:25 PM, Jim Bell wrote:

>
>
> On 2015-08-11 11:47 PM, Edward Diener wrote:
>> On 8/11/2015 9:40 PM, Tom Kent wrote:
>>> Can you document it somewhere? I'd be interested in adding clang/gcc on
>>> mingw runs to the ones I do on windows, but I had never had much luck
>>> getting them up and running.
>>
>> I thought I had figured it out but it is still not working when trying
>> to run the regression tests. I am getting messages as if the
>> particular version of mingw-64/gcc used in a regression test is not in
>> my path when some executable is being run or tested ( so and so
>> mingw-64/gcc DLL can not be found ).
>>
>> Yet when I manually test out libraries in the latest boost trunk
>> everything is fine. I can see when I run tests that Boost build is
>> prepending the path to the mingw-64/gcc version I am using to the
>> Windows PATH so that when the test is run, everything is found.
>
> I have mingw tests for mingw-32, mingw-w64 gcc 4.9, 4.8, 4.7, 4.6, 4.5,
> and 4.4.  Also the mingw-gcc that ships with Qt 5.4, Qt 5.2 and Qt 4.

Do you compile/link from each particular mingw's bin directory when you
test ? Or do you put each mingw's bin directory in your Windows PATH
when you test ? Because my experience is that you can't just invoke gcc
or g++ without getting compile/link errors unless the particular 'bin'
directory is in the PATH.

>
> I don't recall everything I did to get it working, but I'll fire one
> back up tomorrow.

Whatever information you can give would be helpful.

>
> As I recall, clang wouldn't build one kind of library (dynamic or
> static, I don't recall which), and that killed the results.  Has that
> changed?
>
>
>>
>> Soemhow the regression tests are not doing the same thing in running
>> the tests that I do manually to test any particular library. I will be
>> trying to find out what that is.
>>
>>>
>>> Tom
>>>
>>> On Tue, Aug 11, 2015 at 7:20 PM, Edward Diener <[hidden email]
>>> <mailto:[hidden email]>> wrote:
>>>
>>>     On 8/11/2015 4:38 PM, Edward Diener wrote:
>>>
>>>         For a long time now we have had no regression tests for
>>> mingw/gcc or
>>>         clang targeting gcc on Windows. The only regression tests for
>>>         Windows
>>>         are for various releases of VC++.
>>>
>>>         I have limited resources but I have a laptop usually sitting
>>> idle,
>>>         except for occasional travel where I take it with me, and I am
>>>         set up to
>>>         run tests on that machine for mingw/gcc and clang on Windows.
>>>
>>>         However mingw/gcc and clang have limitations when running tests
>>>         in that,
>>>         both relying on various mingw/gcc implementations, the path
>>> to the
>>>         implementation must be added at the beginning of the PATH before
>>>         running
>>>         any of the tests. I have already argued with the mingw-64 people
>>>         about
>>>         this necessity but they are adamant that this should be the case
>>>         even
>>>         just to compile/link properly ( and have setup their directory
>>>         structure
>>>         to enforce it ), and I don't want to waste my breath further
>>>         with them.
>>>
>>>         Currently I have a batch file that does that for me when running
>>>         tests
>>>         for any particular library, but I don't know how that can be
>>>         achieved
>>>         when running the regression tests unless possibly I run
>>>         regression tests
>>>         for only a single toolset at a time, and manipulate the PATH
>>>         accodingly.
>>>         But that is really time consuming since evidently all of Boost
>>>         must be
>>>         downloaded to the run directory each time. Is there an easy
>>>         solution to
>>>         this or do I have to look at run.py and try modify it
>>>         accordingly ( I
>>>         know Python well ) ?
>>>
>>>
>>>     I figured out what my problem was running multiple tests, and how to
>>>     achieve regression testing with clang and gcc on Windows.
>>>
>>>
>>>
>>>         Also I notice on the Boost web site regression test page (
>>> http://www.boost.org/development/running_regression_tests.html )
>>>         that
>>>         the options of the regression tests are somewhat documented but
>>>         none of
>>>         the commands are documented. Is there further documentation
>>>         about the
>>>         regression test commands anywhere ?
>>
>>

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Edward Diener-3
In reply to this post by Jim Bell
On 8/12/2015 11:25 PM, Jim Bell wrote:

>
>
> On 2015-08-11 11:47 PM, Edward Diener wrote:
>> On 8/11/2015 9:40 PM, Tom Kent wrote:
>>> Can you document it somewhere? I'd be interested in adding clang/gcc on
>>> mingw runs to the ones I do on windows, but I had never had much luck
>>> getting them up and running.
>>
>> I thought I had figured it out but it is still not working when trying
>> to run the regression tests. I am getting messages as if the
>> particular version of mingw-64/gcc used in a regression test is not in
>> my path when some executable is being run or tested ( so and so
>> mingw-64/gcc DLL can not be found ).
>>
>> Yet when I manually test out libraries in the latest boost trunk
>> everything is fine. I can see when I run tests that Boost build is
>> prepending the path to the mingw-64/gcc version I am using to the
>> Windows PATH so that when the test is run, everything is found.
>
> I have mingw tests for mingw-32, mingw-w64 gcc 4.9, 4.8, 4.7, 4.6, 4.5,
> and 4.4.  Also the mingw-gcc that ships with Qt 5.4, Qt 5.2 and Qt 4.
>
> I don't recall everything I did to get it working, but I'll fire one
> back up tomorrow.

I noticed that you were contibuting mingw/gcc tests for Windows and then
you stopped doing so. Is it possible to peridically run those tests
again, or is is taking up too much of your time and resources ?

I am going to attempt again to contribute my own gcc, and perhaps even
clang, tests for Windows, although clang is much more error-prone when
dealing with non-header only libraries.


_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Jim Bell


On 2015-10-10 12:25 AM, Edward Diener wrote:

> On 8/12/2015 11:25 PM, Jim Bell wrote:
>>
>>
>> On 2015-08-11 11:47 PM, Edward Diener wrote:
>>> ...
>>
>> I have mingw tests for mingw-32, mingw-w64 gcc 4.9, 4.8, 4.7, 4.6, 4.5,
>> and 4.4.  Also the mingw-gcc that ships with Qt 5.4, Qt 5.2 and Qt 4.
>>
>> I don't recall everything I did to get it working, but I'll fire one
>> back up tomorrow.
>
> I noticed that you were contibuting mingw/gcc tests for Windows and
> then you stopped doing so. Is it possible to peridically run those
> tests again, or is is taking up too much of your time and resources ?
>
> I am going to attempt again to contribute my own gcc, and perhaps even
> clang, tests for Windows, although clang is much more error-prone when
> dealing with non-header only libraries.
>

I'm glad to periodically run my battery of tests, but would request that
at least the master test results stay in the regression results matrix
for a longer period of time.
_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Rene Rivera-2
On Sun, Oct 18, 2015 at 9:14 PM, Jim Bell <[hidden email]> wrote:

On 2015-10-10 12:25 AM, Edward Diener wrote:
On 8/12/2015 11:25 PM, Jim Bell wrote:


On 2015-08-11 11:47 PM, Edward Diener wrote:
...

I have mingw tests for mingw-32, mingw-w64 gcc 4.9, 4.8, 4.7, 4.6, 4.5,
and 4.4.  Also the mingw-gcc that ships with Qt 5.4, Qt 5.2 and Qt 4.

I don't recall everything I did to get it working, but I'll fire one
back up tomorrow.

I noticed that you were contibuting mingw/gcc tests for Windows and then you stopped doing so. Is it possible to peridically run those tests again, or is is taking up too much of your time and resources ?

I am going to attempt again to contribute my own gcc, and perhaps even clang, tests for Windows, although clang is much more error-prone when dealing with non-header only libraries.


I'm glad to periodically run my battery of tests, but would request that at least the master test results stay in the regression results matrix for a longer period of time.

How long?


--
-- Rene Rivera
-- Grafik - Don't Assume Anything
-- Robot Dreams - http://robot-dreams.net
-- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Edward Diener-3
In reply to this post by Jim Bell
On 10/18/2015 10:14 PM, Jim Bell wrote:

>
>
> On 2015-10-10 12:25 AM, Edward Diener wrote:
>> On 8/12/2015 11:25 PM, Jim Bell wrote:
>>>
>>>
>>> On 2015-08-11 11:47 PM, Edward Diener wrote:
>>>> ...
>>>
>>> I have mingw tests for mingw-32, mingw-w64 gcc 4.9, 4.8, 4.7, 4.6, 4.5,
>>> and 4.4.  Also the mingw-gcc that ships with Qt 5.4, Qt 5.2 and Qt 4.
>>>
>>> I don't recall everything I did to get it working, but I'll fire one
>>> back up tomorrow.
>>
>> I noticed that you were contibuting mingw/gcc tests for Windows and
>> then you stopped doing so. Is it possible to peridically run those
>> tests again, or is is taking up too much of your time and resources ?
>>
>> I am going to attempt again to contribute my own gcc, and perhaps even
>> clang, tests for Windows, although clang is much more error-prone when
>> dealing with non-header only libraries.
>>
>
> I'm glad to periodically run my battery of tests, but would request that
> at least the master test results stay in the regression results matrix
> for a longer period of time.

I don't know how it is determined how long test results stay in the
regression tests result matrix for either 'develop' or 'master'. But
even if you could run your gcc on Windows test once a week I would view
this as a big plus for the regression test results on Windows.

Unfortunately for me my current laptop, which is adequate for small
programming efforts, is too slow to run Boost regression tests. It takes
more than 24 hours to run regression tests on my laptop for a single
compiler. I really need to get a faster laptop in order to contribute
boost regression tests when running on it.

_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Jim Bell
In reply to this post by Rene Rivera-2


On 2015-10-18 9:56 PM, Rene Rivera wrote:
On Sun, Oct 18, 2015 at 9:14 PM, Jim Bell <[hidden email]> wrote:

On 2015-10-10 12:25 AM, Edward Diener wrote:
On 8/12/2015 11:25 PM, Jim Bell wrote:


On 2015-08-11 11:47 PM, Edward Diener wrote:
...

I have mingw tests for mingw-32, mingw-w64 gcc 4.9, 4.8, 4.7, 4.6, 4.5,
and 4.4.  Also the mingw-gcc that ships with Qt 5.4, Qt 5.2 and Qt 4.

I don't recall everything I did to get it working, but I'll fire one
back up tomorrow.

I noticed that you were contibuting mingw/gcc tests for Windows and then you stopped doing so. Is it possible to peridically run those tests again, or is is taking up too much of your time and resources ?

I am going to attempt again to contribute my own gcc, and perhaps even clang, tests for Windows, although clang is much more error-prone when dealing with non-header only libraries.


I'm glad to periodically run my battery of tests, but would request that at least the master test results stay in the regression results matrix for a longer period of time.

How long?

How about 90 days? The audience for master is very different than for develop.



_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing
Reply | Threaded
Open this post in threaded view
|

Re: Adding regression tests for mingw(-64)/gcc and clang on Windows

Jim Bell
In reply to this post by Edward Diener-3


On 2015-10-18 10:22 PM, Edward Diener wrote:

> On 10/18/2015 10:14 PM, Jim Bell wrote:
>>
>>
>> On 2015-10-10 12:25 AM, Edward Diener wrote:
>>> On 8/12/2015 11:25 PM, Jim Bell wrote:
>>>>
>>>>
>>>> On 2015-08-11 11:47 PM, Edward Diener wrote:
>>>>> ...
>>>>
>>>> I have mingw tests for mingw-32, mingw-w64 gcc 4.9, 4.8, 4.7, 4.6,
>>>> 4.5,
>>>> and 4.4.  Also the mingw-gcc that ships with Qt 5.4, Qt 5.2 and Qt 4.
>>>>
>>>> I don't recall everything I did to get it working, but I'll fire one
>>>> back up tomorrow.
>>>
>>> I noticed that you were contibuting mingw/gcc tests for Windows and
>>> then you stopped doing so. Is it possible to peridically run those
>>> tests again, or is is taking up too much of your time and resources ?
>>>
>>> I am going to attempt again to contribute my own gcc, and perhaps even
>>> clang, tests for Windows, although clang is much more error-prone when
>>> dealing with non-header only libraries.
>>>
>>
>> I'm glad to periodically run my battery of tests, but would request that
>> at least the master test results stay in the regression results matrix
>> for a longer period of time.
>
> I don't know how it is determined how long test results stay in the
> regression tests result matrix for either 'develop' or 'master'. But
> even if you could run your gcc on Windows test once a week I would
> view this as a big plus for the regression test results on Windows.

I can only run one set per day, so cycling through them all takes a full
week.


_______________________________________________
Boost-Testing mailing list
[hidden email]
http://lists.boost.org/mailman/listinfo.cgi/boost-testing