On http://test.winehq.org/data/200404192305/ the "next build" and "previous build" buttons are broken. I get a error message, saying "You don't have permission to access /site on this server."
Ivan.
"Ivan Leo Murray-Smith" puoti@inwind.it writes:
On http://test.winehq.org/data/200404192305/ the "next build" and "previous build" buttons are broken. I get a error message, saying "You don't have permission to access /site on this server."
Yes, that's intentional. :-) (ie. not implemented yet)
Another thing, why is it a zero "0" on all the green rectangles? Looks kind of sad to me...
Ivan Leo Murray-Smith wrote:
On http://test.winehq.org/data/200404192305/ the "next build" and "previous build" buttons are broken. I get a error message, saying "You don't have permission to access /site on this server."
Ivan.
Jakob Eriksson jakov@vmlinux.org writes:
Another thing, why is it a zero "0" on all the green rectangles? Looks kind of sad to me...
For consistency. But it's time to come forward with ideas about what and how to show in the summaries!
Ferenc Wagner wrote:
For consistency. But it's time to come forward with ideas about what and how to show in the summaries!
Summaries? I don't understand... which summaries of what?
regards, Jakob
Jakob Eriksson jakov@vmlinux.org writes:
Ferenc Wagner wrote:
For consistency. But it's time to come forward with ideas about what and how to show in the summaries!
Summaries? I don't understand... which summaries of what?
Oh man... Read the main headline on the page we are talking about! The one which starts with 'Main summary...' :) I'm talking about the only page we have at the moment.
Ferenc Wagner wrote:
Jakob Eriksson jakov@vmlinux.org writes:
Ferenc Wagner wrote:
For consistency. But it's time to come forward with ideas about what and how to show in the summaries!
Summaries? I don't understand... which summaries of what?
Oh man... Read the main headline on the page we are talking about! The one which starts with 'Main summary...' :) I'm talking about the only page we have at the moment.
That's it! I'm going to bed.
On a side note, how about this:
int running_on_wine () { HKEY version_key; long size = 0;
RegCreateKeyEx (HKEY_LOCAL_MACHINE, "Software", 0, NULL, REG_OPTION_NON_VOLATILE, KEY_ALL_ACCESS, NULL, &version_key, NULL);
return ERROR_SUCCESS == RegQueryValue(version_key, "Wine", NULL, &size); }
void print_version () { OSVERSIONINFOEX ver; BOOL ext; static const TCHAR wine[128] = {"Wine"};
ver.dwOSVersionInfoSize = sizeof(OSVERSIONINFOEX); if (!(ext = GetVersionEx ((OSVERSIONINFO *) &ver))) { ver.dwOSVersionInfoSize = sizeof(OSVERSIONINFO); if (!GetVersionEx ((OSVERSIONINFO *) &ver)) report (R_FATAL, "Can't get OS version."); }
if (running_on_wine()) { /* Make a an obvious signature for Wine */ ext = 1;
ver.dwMajorVersion = 1; ver.dwMinorVersion = 1; ver.dwBuildNumber = 1; ver.dwPlatformId = 1; strncpy (ver.szCSDVersion, wine, sizeof(wine)); }
xprintf (" dwMajorVersion=%ld\n dwMinorVersion=%ld\n" " dwBuildNumber=%ld\n PlatformId=%ld\n szCSDVersion=%s\n", ver.dwMajorVersion, ver.dwMinorVersion, ver.dwBuildNumber, ver.dwPlatformId, ver.szCSDVersion);
if (!ext) return;
xprintf (" wServicePackMajor=%d\n wServicePackMinor=%d\n" " wSuiteMask=%d\n wProductType=%d\n wReserved=%d\n", ver.wServicePackMajor, ver.wServicePackMinor, ver.wSuiteMask, ver.wProductType, ver.wReserved); }
Jakob Eriksson jakov@vmlinux.org writes:
On a side note, how about this:
int running_on_wine () { HKEY version_key; long size = 0;
RegCreateKeyEx (HKEY_LOCAL_MACHINE,
Yes, checking the registry is one way to detect Wine. But not bulletproof, I'm afraid: what if somebody uses a real Windows partition/installation to run Wine with a shared registry? Won't Wine enter it's keys into the Windows registry?
On Wed, 21 Apr 2004, Ferenc Wagner wrote:
Yes, checking the registry is one way to detect Wine. But not bulletproof, I'm afraid: what if somebody uses a real Windows partition/installation to run Wine with a shared registry? Won't Wine enter it's keys into the Windows registry?
A much better method would be
int running_on_wine() { HMODULE module = LoadLibrary("ntdll"); FARPROC proc = 0; if (module) { proc = GetProcAddress(module, "wine_get_unix_file_name"); FreeLibrary(module); } return proc != 0; }
Dimitrie O. Paun wrote:
On Wed, 21 Apr 2004, Ferenc Wagner wrote:
Yes, checking the registry is one way to detect Wine. But not bulletproof, I'm afraid: what if somebody uses a real Windows partition/installation to run Wine with a shared registry? Won't Wine enter it's keys into the Windows registry?
A much better method would be
int running_on_wine() { HMODULE module = LoadLibrary("ntdll"); FARPROC proc = 0; if (module) { proc = GetProcAddress(module, "wine_get_unix_file_name"); FreeLibrary(module); } return proc != 0; }
That's awesome, thanks!
regards, Jakob
Ferenc Wagner wrote:
For consistency. But it's time to come forward with ideas about what and how to show in the summaries!
I think it's pretty nice as it is. But maybe it't just the raw shock of suddenly having a distributed test system in place, that actually works and has pretty colors.
Maybe one slight suggestion so far:
when you click on one of the numbers to see the test output, the summary line appears at the bottom of test output. Like this one: vartest: 553559462 tests executed, 0 marked as todo, 4113 failures.
It would be kinda neat to have that line at the top of the log instead.
regards, Jakob
Jakob Eriksson jakov@vmlinux.org writes:
when you click on one of the numbers to see the test output, the summary line appears at the bottom of test output. Like this one:
vartest: 553559462 tests executed, 0 marked as todo, 4113 failures.
It would be kinda neat to have that line at the top of the log instead.
If you hoover your mouse over that number, you get something similar in a tooltip popup.
Ferenc Wagner wrote:
Jakob Eriksson jakov@vmlinux.org writes:
vartest: 553559462 tests executed, 0 marked as todo, 4113 failures.
It would be kinda neat to have that line at the top of the log instead.
If you hoover your mouse over that number, you get something similar in a tooltip popup.
Oh! That's so NICE! Thanks, I was much to impatient to hover by mistake. ;-)
regards, Jakob