Hi!

I have not touched Windows for a very long time. For about a month I’ve been trying to start CI testing of druntime locally but nothing works for me.

Currently I tried:

https://github.com/joaope/LocalAppVeyor - isn't works because CI script uses (proprietary?) "Start-FileDownload"

Build by wiki instructions. It contains step:
- Building DMD
You should be able to build DMD using the visual studio solution found in: dmd\src\vcbuild A typical choice is to build the 64-bit debug version (the VisualD options are named 'Release' and 'x64').

VS 2017 (used in AppVeyor script) says what current dmd project isn't compatible with VS 2017

I don’t know what to do next.

I develop under Linux, so only tests are important.

On Monday, 6 April 2020 at 06:29:32 UTC, Denis Feklushkin wrote:
> Hi!
>
> I have not touched Windows for a very long time. For about a month I’ve been trying to start CI testing of druntime locally but nothing works for me.

Here I miss various unsuccessful attempts which, in principle, could not lead to success and learning. So this is the total time spent.

This is a one-time task for me, so maybe it is possible that someone can share a virtual machine which "just works"?

Just make a pull request on github and let the tests run there. It's a pain in the ass to setup, and you have to deal with new bugs constantly as the build scripts are ever changing.

On Monday, 6 April 2020 at 16:36:44 UTC, Arine wrote:
> Just make a pull request on github and let the tests run there.

I usually do it by that way. But this time there will be a lot of attempts to change something in which I do not really know (most likely "voodoo programming" of .bat files) so a lot of time will be spent.

On Monday, 6 April 2020 at 06:29:32 UTC, Denis Feklushkin wrote:
> Hi!
>
> I have not touched Windows for a very long time. For about a month I’ve been trying to start CI testing of druntime locally but nothing works for me.
>
> Currently I tried:
>
> https://github.com/joaope/LocalAppVeyor - isn't works because CI script uses (proprietary?) "Start-FileDownload"
>
> Build by wiki instructions. It contains step:
> - Building DMD
> You should be able to build DMD using the visual studio solution found in: dmd\src\vcbuild A typical choice is to build the 64-bit debug version (the VisualD options are named 'Release' and 'x64').
>
> VS 2017 (used in AppVeyor script) says what current dmd project isn't compatible with VS 2017

Did you try it locally?

> I don’t know what to do next.
>
> I develop under Linux, so only tests are important.

Have a look at what the CI scripts are doing and don't bail on File-Download as that's only required to download the required tools once.

Start having a look either here:

https://github.com/dlang/dmd/blob/master/.azure-pipelines/windows.sh

Or if you want to use Visual Studio:

https://github.com/dlang/dmd/blob/master/.azure-pipelines/windows-msbuild.bat

Building DMD should be very easy. You can either use the VS Studio solution or call run.d yourself.
For druntime, it then really just bails down to calling make with the right parameters (n.b. the DigitalMars Make that everyone dislikes for very good reasons, but that's a different story).

Also, the CI tools test a lot more than you need, so I would only focus on exactly the part which you need.

On Tuesday, 7 April 2020 at 08:48:52 UTC, Seb wrote:
> On Monday, 6 April 2020 at 06:29:32 UTC, Denis Feklushkin wrote:
>> Hi!
>>
>> I have not touched Windows for a very long time. For about a month I’ve been trying to start CI testing of druntime locally but nothing works for me.
>>
>> Currently I tried:
>>
>> https://github.com/joaope/LocalAppVeyor - isn't works because CI script uses (proprietary?) "Start-FileDownload"
>>
>> Build by wiki instructions. It contains step:
>> - Building DMD
>> You should be able to build DMD using the visual studio solution found in: dmd\src\vcbuild A typical choice is to build the 64-bit debug version (the VisualD options are named 'Release' and 'x64').
>>
>> VS 2017 (used in AppVeyor script) says what current dmd project isn't compatible with VS 2017
>
> Did you try it locally?

Yes

>
>> I don’t know what to do next.
>>
>> I develop under Linux, so only tests are important.
>
> Have a look at what the CI scripts are doing and don't bail on File-Download as that's only required to download the required tools once.

There are needed too many actions except File-Download.

> Building DMD should be very easy. You can either use the VS Studio solution or call run.d yourself.
> For druntime, it then really just bails down to calling make with the right parameters (n.b. the DigitalMars Make that everyone dislikes for very good reasons, but that's a different story).

Thanks!
Actually now I know how to run druntime Windows tests:

1. install DMD Windows package
2. it is need to use special console named "x86 native tools command prompt"
3. run: make -f win64.mak DMD=dmd CC=cl auto-tester-build auto-tester-test