Mikolaj Zalewski wrote:
> I now start to understand the structure of the tests. Do you know if
> there is a known regression in current Wine that I could use to try to
> do some scripting? If not I could use wine-0.9.43 as a reference with
> it's Win16 regression that affects the pptviewer and exc
Hi Mikolaj,
nice work!
I saw that you successfully ran cxtest.sh script on your machine and
submitted results. Currently, we are in process of setuping cxtest.sh
(tests Wine make test, Picasa, WinZip, WordViewer, ExcelViewer, PptViewer)
and 3dMark2000 tests nightly on our testing machines. Once w
> Hello Martin
>
> If you cd into the 3DMark2000 install directory and run it from there
> does it work?
>
> Tom
Thanks Tom, that was it. I got a bit further, the message I got this time is:
3DMark could not initialize your 3D Accelerator. Try to downgrade your
display settings.
I played with
> is wined3d built?
That was it - I was missing some dev libs. Thanks!
I fixed that, now I am receiving this error:
Not all of the E2 drivers were found. Check that you have 3DMark installed
properly.
Attached are the log files from installation and run.
Martin
3dmark2000log.tar.gz
Descriptio
> Do you have HKCU/Software/Wine/Direct3D/DirectDrawRenderer set to "gdi"
> perhaps? This disables D3D support altogether. You could try with a
> fresh .wine, it should run 3dmark2000 and 2001 out of the box.
I tried latest WineHq, it created ~/.wine directory and installed
3DMark2000 correctly,
Hello Stefan!
> It is without CxTest and without VNC. I do have HW acceleration and OpenGL
> (GLX) enabled. Attached is output of xdpyinfo.
>
> I am going to try whether 3DMark2001 works.
3DMark2001 behaves the same way. Note this is long lasting bug, I remember
on WineConf 2006 I was able to r
Stefan Dösinger wrote:
> Am Dienstag, 31. Juli 2007 16:42 schrieb martin pilka:
>> Hello Stefan,
>>
>> link works, I was able to run your test. Installation is ok, however test
>> itself ends with '3DMark Error': '3DMark needs DirectX 7 and proper d
r newer is correctly detected during
installation process.
Is it a bug in my configuration, or did I hit some Wine error?
Thanks,
Martin
Stefan Dösinger wrote:
> Am Dienstag, 31. Juli 2007 12:28 schrieb martin pilka:
>>> With Francois' help I could build a test package for 3DMark2000 n
> With Francois' help I could build a test package for 3DMark2000 now:
>
> http://stud4.tuwien.ac.at/~e0526822/3dmark2000.tar.bz2
>
> It runs two tests, one at 640x480, another one at 1024x768, writes the
> results
> to a file and reads the file back. No benchmark results are sent to the
> ser
Stefan Dösinger wrote:
> The roadmap looks good to me. I am missing some clarification how to deal
> with
> different hardware configurations.
This is how CxTest supports it now:
* There is 1:1 association between submitter and his configuration, i.e.
"Stefan - Desktop" --> "AMD 1.8 GHz 1 GB
Hello Stefan,
following is specification proposal for first few iterations. It is more
focused on functionality than technical details. Feel free to comment.
1st iteration
=
* We take your 3dMark test, adjust it a bit and make it run and submit
results regularly on one of our testin
Hello Stefan!
> If the pages are important I can go to Vienna and boot the server, but it
> would be a
> 6 hour travel just to press a power button.
Not really important, I just wanted to have closer look what values you put
into your graphs, however I come with something and then we tweak it
Stefan Dösinger wrote:
> Yes, thats essentially what we need. I've been setting up a quick and
> dirty test site myself, with a few lines of php and gnuplot:
>
> http://84.112.174.163/~stefan/laptop/3dmark2000/results.php
Stefan,
could you put the link life again? Or send me screenshots of it. I a
Hello Dan!
> I'm sure there will always be some tests that are
> better written directly in CxTest, but I'm going to
> try to push yawt forward, too. With
> luck we'll have the two test systems working
> well together in a month or two.
YAWT looks interesting, I also had a look to AutoHotKey, a
Dan,
on YAWT homepage, I read:
"YAWT can be used either standalone, or as part of the cxtest.org automated
regression test suite for Wine"
You mean, it can generate result emails which can be parsed by CxTest server?
Or how does it work?
Thanks,
Martin
Dan Kegel wrote:
> Vit Hrachovy wrote:
Francois Gouget wrote:
> You could also write some software to automatically analyze this data on
> the server but that seems overkill.
Yes, we tried this while ago and it was really overkill. I believe results
should be analyzed by man, but he needs user friendly formatted information
for this.
Detlef Riekenberg wrote:
> On Di, 2007-06-26 at 13:06 +0200, Stefan Dösinger wrote:
>
>> Appart of controlling the apps we'll need some programs to start the
>> application scripts, extract the results and do something with them.
>
>> We also need some database to collect the results.
>
> We c
>> Running applications with different log levels, tracing output,
>> comparing screenshots with different levels of fuzzy comparaion
>> - it's not faraway.
> How would fuzzy comparison work?
See projects findimagedupes and gqview (duplicate window, hit 'D' in gqview
interface), both presented as
Stefan Dösinger wrote:
> --no-vnc works fine for me for playing tests, but it does not work for
> recording tests.
VNC was never hard requirement of CxTest, we are using it to guarantee same
testing environment everywhere. However, it is been a while I ran it without
VNC, let me check.
Martin
Hello Stefan!
> We don't have to transfer all the rendering screenshots over VNC though.
> I am CCing Martin Pilka on this, maybe he can give us some more insight.
I apologize for late answer - I was (and still am) ill. However, now I read
whole thread, let me summarize the goal
I see Bryan already submitted patch for this. Going to try to install
libxml-dev thing in meantime.
Thanks,
Martin
> Hello,
>
> I just tried to compile Wine on Ubuntu 6.06 and Ubuntu 7.04 (both updated). On
> both machines, I got following error:
>
> make[2]: Entering directory `/home/mpilka/c
Hello,
I just tried to compile Wine on Ubuntu 6.06 and Ubuntu 7.04 (both updated). On
both machines, I got following error:
make[2]: Entering directory `/home/mpilka/cxtest/wine/dlls/msxml3'
gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__
-DCOM_NO_WINDOWS_H -D_REENTRANT -fPIC -Wall
Hello,
automated CxTest testing shows WinZip regression:
Jan 8 - WinZip ran 9 times (5 Francois + 4 Jozef), all succeeded
Jan 9 - WinZip ran 1 time (Francois), failed with
http://www.cxtest.org/triage/failures?dl=364121
(Out of resources error, unable to continue)
Jan 10 - WinZip ran 2 times (1
> Actually the shlfolder test seems to succeed on your machine and
> it is the shlexec and shlfileop tests that are failing (and are working
> for me).
> Are you using a freshly generated ~/.wine directory?
Before each "make test", ~/.wine dir is erased and generated again. Is that
enough?
Mar
> Unfortunately I don't have the exact date because I did not keep a
> history of my nightly test runs (but I do now).
Have a look here:
http://www.cxtest.org/reports/last_week?from%5B1%5D=9&from%5B2%5D=1&from%5B0%5D=2006&from%5B3%5D=23&from%5B4%5D=59&to%5B1%5D=10&to%5B2%5D=27&to%5B0%5D=2006&to%
Hello Dan,
interesting, and actually not hard to do. I created bug for this (in our
internal CxTest bug list).
Thanks,
Martin
Dan Kegel wrote:
> It occurred to me that one problem with cxtest.org
> is that it's hard to browse the results of a particular application -
> and that it would be real
26 matches
Mail list logo
