Hi Aric, failed again on second run, http://buildbot.kegel.com:8010/builders/runtests-default/builds/209
Failing tests are comctl32_test.exe.so listview.c comctl32_test.exe.so updown.c user32_test.exe.so edit.c
On Tue, Oct 11, 2011 at 1:26 PM, Dan Kegel dank@kegel.com wrote:
Hey Aric, don't know if I trust the bot at the moment, but it says the tests failed here... I'll rerun them to see if the failure is repeatable.
---------- Forwarded message ---------- From: buildbot@kegel.com Date: Tue, Oct 11, 2011 at 1:21 PM Subject: Re: 79794: Help Test Please: use uniscribe in the single line edit control To: dank@kegel.com, wine-tests-results@winehq.org
This is an experimental automated build and test service. Please feel free to ignore this email while we work the kinks out.
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests-default while building Wine. Full details are available at: http://buildbot.kegel.com/builders/runtests-default/builds/186 (though maybe not for long, as I'm still reinstalling the buildbot periodically while experimenting) BUILD FAILED: failed shell_3
Errors: alarum: Timeout! Killing child ../../../wine. alarum: failed command was ../../../wine comctl32_test.exe.so listview.c alarum: ../../../wine terminated abnormally make: *** [listview.ok] Error 99 alarum: Timeout! Killing child ../../../wine. alarum: failed command was ../../../wine comctl32_test.exe.so updown.c alarum: ../../../wine terminated abnormally make: *** [updown.ok] Error 99
- Call to xpconnect wrapped JSObject produced this error: *
- Call to xpconnect wrapped JSObject produced this error: *
alarum: failed command was ../../../wine user32_test.exe.so edit.c edit.c:1138: Test failed: expected 1 got 0 edit.c:1156: Test failed: expected 1 got 0 edit.c:1174: Test failed: expected 1 got 0 make: *** [edit.ok] Error 3 GnuTLS error: GnuTLS internal error.
Thank Dan, I had not gotten to a full test run.
I will look into those.
-aric
On 10/11/11 8:01 PM, Dan Kegel wrote:
Hi Aric, failed again on second run, http://buildbot.kegel.com:8010/builders/runtests-default/builds/209
Failing tests are comctl32_test.exe.so listview.c comctl32_test.exe.so updown.c user32_test.exe.so edit.c
On Tue, Oct 11, 2011 at 1:26 PM, Dan Kegeldank@kegel.com wrote:
Hey Aric, don't know if I trust the bot at the moment, but it says the tests failed here... I'll rerun them to see if the failure is repeatable.
---------- Forwarded message ---------- From:buildbot@kegel.com Date: Tue, Oct 11, 2011 at 1:21 PM Subject: Re: 79794: Help Test Please: use uniscribe in the single line edit control To: dank@kegel.com, wine-tests-results@winehq.org
This is an experimental automated build and test service. Please feel free to ignore this email while we work the kinks out.
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests-default while building Wine. Full details are available at: http://buildbot.kegel.com/builders/runtests-default/builds/186 (though maybe not for long, as I'm still reinstalling the buildbot periodically while experimenting) BUILD FAILED: failed shell_3
Errors: alarum: Timeout! Killing child ../../../wine. alarum: failed command was ../../../wine comctl32_test.exe.so listview.c alarum: ../../../wine terminated abnormally make: *** [listview.ok] Error 99 alarum: Timeout! Killing child ../../../wine. alarum: failed command was ../../../wine comctl32_test.exe.so updown.c alarum: ../../../wine terminated abnormally make: *** [updown.ok] Error 99
- Call to xpconnect wrapped JSObject produced this error: *
- Call to xpconnect wrapped JSObject produced this error: *
alarum: failed command was ../../../wine user32_test.exe.so edit.c edit.c:1138: Test failed: expected 1 got 0 edit.c:1156: Test failed: expected 1 got 0 edit.c:1174: Test failed: expected 1 got 0 make: *** [edit.ok] Error 3 GnuTLS error: GnuTLS internal error.