Re: [Scons-dev] Appveyor testing platforms

2019-01-30 Thread Bill Deegan
By default scons does not use  os.environ's PATH.
The test framework does for some tools though ideally SCons would cover
reasonable default paths for windows tools.

If the install path in appveyor is not a reasonable default, then it may
make sense to have the test find the path and provide it to the test logic.
Otherwise it's more "sconsian" to add the reasonable default into the tool
logic.

Can you add information about the tools provided to the PR summary?
Just trying to make it easier for folks to trace back any logic changes to
infrastructure (and code) to the PR's and their expected effects.



On Wed, Jan 30, 2019 at 9:40 AM Daniel Moody  wrote:

> I'm fairly certain that even though most of these tools are installed,
> they are not part of the default PATH, so you may need to add them near the
> top of the appveyor file where we add some other things like mingw. Also
> depends on how the tools are being found in scons code, is the os.environ
> used at all or is it just assumed default paths? You may have to ask
> appveyor support where the WIX tools are installed. Do you know a common
> place they would be? The new appveyor.yml should call set to print the env
> to the log, so you could check the path.
>
> On Wed, Jan 30, 2019 at 11:26 AM Mats Wichmann  wrote:
>
>> On 1/30/19 10:12 AM, Daniel Moody wrote:
>> > Windows Server 2012:
>> > Visual Studio 2008 Express
>> > Visual Studio 2010 Pro/Express
>> > Visual Studio 2012 Pro/Express
>> > Visual Studio 2013 Community
>> > Visual Studio 2015 Community
>> >
>> > Windows Server 2016:
>> > Visual Studio 2015 Community
>> > Visual Studio 2017 Community
>> >
>> > Also software versions for the different Windows can be found:
>> > https://www.appveyor.com/docs/windows-images-software/
>>
>> Okay, this was interesting... I've tried adding wix toolset
>> (https://github.com/SCons/scons/pull/3204), and that causes the build to
>> break.  But according to that chart, it's already included, under Misc
>> SDKs:
>>
>> WiX Toolset 3.11.0.1701
>>
>> So why are we not finding the preinstalled one?
>>
>> Some of the entries show the paths to look at, but wix isn't one of those.
>>
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev


Re: [Scons-dev] Appveyor testing platforms

2019-01-30 Thread Daniel Moody
I'm fairly certain that even though most of these tools are installed, they
are not part of the default PATH, so you may need to add them near the top
of the appveyor file where we add some other things like mingw. Also
depends on how the tools are being found in scons code, is the os.environ
used at all or is it just assumed default paths? You may have to ask
appveyor support where the WIX tools are installed. Do you know a common
place they would be? The new appveyor.yml should call set to print the env
to the log, so you could check the path.

On Wed, Jan 30, 2019 at 11:26 AM Mats Wichmann  wrote:

> On 1/30/19 10:12 AM, Daniel Moody wrote:
> > Windows Server 2012:
> > Visual Studio 2008 Express
> > Visual Studio 2010 Pro/Express
> > Visual Studio 2012 Pro/Express
> > Visual Studio 2013 Community
> > Visual Studio 2015 Community
> >
> > Windows Server 2016:
> > Visual Studio 2015 Community
> > Visual Studio 2017 Community
> >
> > Also software versions for the different Windows can be found:
> > https://www.appveyor.com/docs/windows-images-software/
>
> Okay, this was interesting... I've tried adding wix toolset
> (https://github.com/SCons/scons/pull/3204), and that causes the build to
> break.  But according to that chart, it's already included, under Misc
> SDKs:
>
> WiX Toolset 3.11.0.1701
>
> So why are we not finding the preinstalled one?
>
> Some of the entries show the paths to look at, but wix isn't one of those.
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev


Re: [Scons-dev] Appveyor testing platforms

2019-01-30 Thread Mats Wichmann
On 1/30/19 10:12 AM, Daniel Moody wrote:
> Windows Server 2012:
> Visual Studio 2008 Express
> Visual Studio 2010 Pro/Express
> Visual Studio 2012 Pro/Express
> Visual Studio 2013 Community
> Visual Studio 2015 Community
> 
> Windows Server 2016:
> Visual Studio 2015 Community
> Visual Studio 2017 Community
> 
> Also software versions for the different Windows can be found:
> https://www.appveyor.com/docs/windows-images-software/

Okay, this was interesting... I've tried adding wix toolset
(https://github.com/SCons/scons/pull/3204), and that causes the build to
break.  But according to that chart, it's already included, under Misc SDKs:

WiX Toolset 3.11.0.1701

So why are we not finding the preinstalled one?

Some of the entries show the paths to look at, but wix isn't one of those.


___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev


Re: [Scons-dev] Appveyor testing platforms

2019-01-30 Thread Daniel Moody
Windows Server 2012:
Visual Studio 2008 Express
Visual Studio 2010 Pro/Express
Visual Studio 2012 Pro/Express
Visual Studio 2013 Community
Visual Studio 2015 Community

Windows Server 2016:
Visual Studio 2015 Community
Visual Studio 2017 Community

Also software versions for the different Windows can be found:
https://www.appveyor.com/docs/windows-images-software/


On Tue, Jan 29, 2019 at 11:52 PM Bill Deegan 
wrote:

> which versions of VS are on each?
>
> On Tue, Jan 29, 2019 at 7:59 PM Daniel Moody  wrote:
>
>> Appveyor CI used with Github only alots 1 job to run at time. It can take
>> 6 - 10 hours to run all the tests on the all the different Windows
>> environments. I would like to reduce the redundancy here a bit to decrease
>> the time it takes for the Windows CI to complete. Appveyor supports two
>> different versions of windows, Windows Server 2012 (like Windows
>> 8) and Windows Server 2016 (like Windows 10). The two versions of windows
>> have different versions of software installed such as Visual Studio, MinGW,
>> etc.
>>
>> *Currently we are running the tests on these platforms:*
>>
>> Windows Server 2012
>> with python 2.7
>> with python 3.6
>>
>> Windows Server 2016
>> with python 2.7
>> with python 3.5
>> with python 3.6
>> with python 3.7
>>
>> *I propose running the tests on these platform configurations:*
>>
>> Windows Server 2012
>> with python 3.5
>> with python 3.6
>>
>> Windows Server 2016
>> with python 2.7
>> with python 3.7
>>
>> This should bring the test down to 4-6 hours. Please let me know if you
>> have any thoughts on the matter.
>>
>>
>> ___
>> Scons-dev mailing list
>> Scons-dev@scons.org
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev


Re: [Scons-dev] Appveyor testing platforms

2019-01-29 Thread Bill Deegan
which versions of VS are on each?

On Tue, Jan 29, 2019 at 7:59 PM Daniel Moody  wrote:

> Appveyor CI used with Github only alots 1 job to run at time. It can take
> 6 - 10 hours to run all the tests on the all the different Windows
> environments. I would like to reduce the redundancy here a bit to decrease
> the time it takes for the Windows CI to complete. Appveyor supports two
> different versions of windows, Windows Server 2012 (like Windows
> 8) and Windows Server 2016 (like Windows 10). The two versions of windows
> have different versions of software installed such as Visual Studio, MinGW,
> etc.
>
> *Currently we are running the tests on these platforms:*
>
> Windows Server 2012
> with python 2.7
> with python 3.6
>
> Windows Server 2016
> with python 2.7
> with python 3.5
> with python 3.6
> with python 3.7
>
> *I propose running the tests on these platform configurations:*
>
> Windows Server 2012
> with python 3.5
> with python 3.6
>
> Windows Server 2016
> with python 2.7
> with python 3.7
>
> This should bring the test down to 4-6 hours. Please let me know if you
> have any thoughts on the matter.
>
>
> ___
> Scons-dev mailing list
> Scons-dev@scons.org
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev


[Scons-dev] Appveyor testing platforms

2019-01-29 Thread Daniel Moody
Appveyor CI used with Github only alots 1 job to run at time. It can take 6
- 10 hours to run all the tests on the all the different Windows
environments. I would like to reduce the redundancy here a bit to decrease
the time it takes for the Windows CI to complete. Appveyor supports two
different versions of windows, Windows Server 2012 (like Windows
8) and Windows Server 2016 (like Windows 10). The two versions of windows
have different versions of software installed such as Visual Studio, MinGW,
etc.

*Currently we are running the tests on these platforms:*

Windows Server 2012
with python 2.7
with python 3.6

Windows Server 2016
with python 2.7
with python 3.5
with python 3.6
with python 3.7

*I propose running the tests on these platform configurations:*

Windows Server 2012
with python 3.5
with python 3.6

Windows Server 2016
with python 2.7
with python 3.7

This should bring the test down to 4-6 hours. Please let me know if you
have any thoughts on the matter.
___
Scons-dev mailing list
Scons-dev@scons.org
https://pairlist2.pair.net/mailman/listinfo/scons-dev