Hi Greg, there is a noisy problem with the WVISTAADM, which causes much tests to be shown as "Failed" in the patchtracker. should we blacklist the Message returned by WVISTAADM or can you fix the underlying problem?
Hi André
there is a noisy problem with the WVISTAADM, which causes much tests to be shown as "Failed" in the patchtracker. should we blacklist the Message returned by WVISTAADM or can you fix the underlying problem?
I'm making some changes to the TestBot infrastructure. This "The specified guest user must be logged in interactively to perform this operation" error did occur before, but it seems it's more prevalent after I upgraded the hypervisor to ESX 4.1. This might take a few days to resolve, for now just ignore that error message.
Greg.
On 12/14/2010 04:44 PM, Greg Geldorp wrote:
Hi André
there is a noisy problem with the WVISTAADM, which causes much tests to be shown as "Failed" in the patchtracker. should we blacklist the Message returned by WVISTAADM or can you fix the underlying problem?
I'm making some changes to the TestBot infrastructure. This "The specified guest user must be logged in interactively to perform this operation" error did occur before, but it seems it's more prevalent after I upgraded the hypervisor to ESX 4.1. This might take a few days to resolve, for now just ignore that error message.
Greg.
Could these changes also explain the new ntdll:exception failures:
http://test.winehq.org/data/tests/ntdll:exception.html
From: Paul Vriens
I'm making some changes to the TestBot infrastructure. This "The specified guest user must be logged in interactively to perform this operation" error did occur before, but it seems it's more prevalent after I upgraded the hypervisor to ESX 4.1. This might take a few days to resolve, for now just ignore that error message.
Could these changes also explain the new ntdll:exception failures:
Yes, I guess that's possible.
Greg.
Am 14.12.2010 22:52, schrieb Greg Geldorp:
From: Paul Vriens
I'm making some changes to the TestBot infrastructure. This "The specified guest user must be logged in interactively to perform this operation" error did occur before, but it seems it's more prevalent after I upgraded the hypervisor to ESX 4.1. This might take a few days to resolve, for now just ignore that error message.
Could these changes also explain the new ntdll:exception failures:
Yes, I guess that's possible.
Greg.
On the other side it seems it turned the 2K8 tests green/yellow without e.g. Pauls oledb32 modification. Cool!