dotnet30 install flaky

[GoogleCodeExporter]

I ran the script

#!/bin/sh
set -x
i=1
export WINEPREFIX=$HOME/.wine
while true
do
    wineserver -k
    rm -rf $WINEPREFIX
    time sh winetricks -q -v dotnet35 > soak-$i.log 2>&1
    sleep 1
    i=`expr $i + 1`
done

overnight.  Out of 104 runs, two failed because of XPSEP (see issue 232),
and one failed during dotnet30 with exit status 67.

According to 
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368542(v=vs.85).aspx
windows error codes are often used as exit status, and 67 is
ERROR_BAD_NET_NAME.  It was starting and stopping the real 
.NET Runtime Optimization Service constantly (dozens of times);
perhaps adding 
    WINEDLLOVERRIDES=ngen.exe,mscorsvw.exe=b
    export WINEDLLOVERRIDES
to the dotnet30 verb would prevent the fault.

Original issue reported on code.google.com by daniel.r...@gmail.com on 18 Jul 2012 at 3:45

• Merged into: #232

[GoogleCodeExporter]

On my AMD box, an overnight soak of 63 runs failed 3 times on XPSEP with status 
194 (issue 232) and 4 times on dotnet30 with status 67.

Oddly, on my i7, an overnight soak of 180 runs of dotnet30 didn't fail once.

Original comment by daniel.r...@gmail.com on 18 Jul 2012 at 3:59

[GoogleCodeExporter]

This is more likely a wine bug, though I think it's more stable now after 
Dmitry's memory cleanup stuff.

Original comment by austinenglish@gmail.com on 29 Jun 2013 at 1:34

[GoogleCodeExporter]

Ran that script on ubuntu 13.04 and wine-1.6-rc3... and it failed on first
try due to http://bugs.winehq.org/show_bug.cgi?id=33450 !

So I added a workaround, and started another overnight run.

Original comment by daniel.r...@gmail.com on 29 Jun 2013 at 2:05

[GoogleCodeExporter]

I think the action is all in XPSEP at this point, marking dup of 232.

Original comment by daniel.r...@gmail.com on 29 Jun 2013 at 4:56

• Changed state: Duplicate