Wine test machine: cw-rx460-wow64

[Jeff Smith]

In trying to get familiar with test.winehq.org, I noticed that under
the Linux test machines, one in particular currently exhibits quite a
few errors that no other machine does: cw-rx460-wow64.  After looking
into the particular errors, several appear to be directly or
indirectly caused by the %windir% and %SystemRoot% environment
variables not being defined.  I don't know the processes involved in
managing the test machines, but I wonder if clearing and
re-initializing the registry for that machine may help.

-- Jeff Smith

[Francois Gouget]

On Wed, 9 Oct 2019, Jeff Smith wrote:
> In trying to get familiar with test.winehq.org, I noticed that under
> the Linux test machines, one in particular currently exhibits quite a
> few errors that no other machine does: cw-rx460-wow64.  After looking
> into the particular errors, several appear to be directly or
> indirectly caused by the %windir% and %SystemRoot% environment
> variables not being defined.  I don't know the processes involved in
> managing the test machines, but I wonder if clearing and
> re-initializing the registry for that machine may help.

The cw-rx460 are a bit of a special case as they are not really part of 
the TestBot but it does not change much in how they operate.

The wineprefix is recreated from scratch with every Wine update so every 
test is run in a brand new Wineprefix, with one exception, the wow32 test.

What happens there is that:
* The 32 and 64 bit Wine is rebuilt.
* Then a new wineprefix is created for the wow64 bit test.
* Then the 64 bit WineTest is run.
* Then the 32 bit WineTest is run in the same wineprefix.

But maybe there is something wrong with the way the wow64 wineprefix is 
created. The code is there:

https://github.com/fgouget/wt-daily/blob/master/wt-bot#L687

And the wt-bot script is called from:

https://github.com/fgouget/wt-daily/blob/master/wt-daily#L786

Either that or the 64 bit build does not really know it has to play nice 
with a 32 bit build too?

[Alexandre Julliard]

Francois Gouget  writes:
> Either that or the 64 bit build does not really know it has to play nice 
> with a 32 bit build too?

If you are running directly from the build tree, the 32-bit build needs
to use --with-wine64.

[Francois Gouget]

On Fri, 11 Oct 2019, Alexandre Julliard wrote:
> Francois Gouget  writes:
> > Either that or the 64 bit build does not really know it has to play nice 
> > with a 32 bit build too?
>
> If you are running directly from the build tree, the 32-bit build needs
> to use --with-wine64.

Wine is indeed run from the build tree but the 'wow32' build gets the 
--with-wine option, both for wt-daily-based builds and the TestBot ones.

* First cw-rx460 builds the 64 bit Wine:
  $ ll wow64/wt-bot-make.log
  -rw-r--r-- 1 winetest winetest 261K Oct 10 13:09 wow64/wt-bot-make.log
  $ cat wow64/wt-bot-make.log
  Running: "../src/configure"  --enable-win64
  [...]
  configure: libhal 64-bit development files not found, no legacy dynamic device support.

configure: Finished.  Do 'make' to compile Wine.

Took 0:56.73 (user 29.50 system 11.08)

Running: "/home/winetest/wt-daily/wt-make"
  [...]
  Wine build complete.

* Then it builds the 32 bit Wine:
  $ ll wow32/wt-bot-make.log
  -rw-r--r-- 1 winetest winetest 271K Oct 10 13:10 wow32/wt-bot-make.log
  $ cat wow32/wt-bot-make.log
  Running: "../src/configure" --with-wine64="/home/winetest/winetest/wow64"
  [...]
  configure: libhal 32-bit development files not found, no legacy dynamic device support.

configure: Finished.  Do 'make' to compile Wine.

Took 0:40.81 (user 26.16 system 10.26)

Running: "/home/winetest/wt-daily/wt-make"
  [...]
  Wine build complete.

Note: Builds are not made from scratch which is why these were fast.