http://bugs.winehq.org/show_bug.cgi?id=18283
Summary: Test Case for Inetmib1 fails because its looking for the test case in the wrong directory Product: Wine Version: 1.1.20 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: testcases AssignedTo: wine-bugs@winehq.org ReportedBy: celticht32@aol.com
The Test Case for Inetmib1 fails because it is unable to find the executable to run.
This occurs in both manual and automatic run of the wine test suite. In the Automatic run there is nothing to tell what the problem is.. the test just fails. When you manually run the test you find out the issue that is the cause of the failure. Here is a paste of the error:
[cahrendt@stinky tests]$ make test ../../../tools/runtest -q -P wine -M inetmib1.dll -T ../../.. -p inetmib1_test.exe.so main.c && touch main.ok Warning: could not find DOS drive for current working directory '/home/cahrendt/wine-git/dlls/inetmib1/tests', starting in the Windows directory. wine: could not load L"C:\windows\system32\inetmib1_test.exe.so": Module not found make: *** [main.ok] Error 126
If you do a ls from the same directory you see the following:
[cahrendt@stinky tests]$ ls inetmib1_test.exe.so main.o Makefile.in testlist.o main.c Makefile testlist.c [cahrendt@stinky tests]$ pwd /home/cahrendt/wine-git/dlls/inetmib1/tests
http://bugs.winehq.org/show_bug.cgi?id=18283
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |austinenglish@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=18283
--- Comment #1 from Juan Lang juan_lang@yahoo.com 2009-04-29 16:19:51 --- This looks like an invalid Wine configuration. Please make sure z: is mapped to / in winecfg. Here's the hint:
Warning: could not find DOS drive for current working directory
http://bugs.winehq.org/show_bug.cgi?id=18283
--- Comment #2 from chris ahrendt celticht32@aol.com 2009-04-29 18:06:35 --- Adding the z: mapping repaired this error.
However if this mapping is required then why not prevent the z: mapping from being deleted in winecfg.
http://bugs.winehq.org/show_bug.cgi?id=18283
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #3 from Austin English austinenglish@gmail.com 2009-04-29 18:18:00 --- (In reply to comment #2)
Adding the z: mapping repaired this error.
However if this mapping is required then why not prevent the z: mapping from being deleted in winecfg.
Wine doesn't require the Z: mapping for many applications to work. If all needed files are mapped under other drives, wine works fine.
If you ran winetest.exe from under C:, it should work fine.
Invalid.
http://bugs.winehq.org/show_bug.cgi?id=18283
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |FIXED
--- Comment #4 from Austin English austinenglish@gmail.com 2009-04-29 18:19:00 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=18283
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |INVALID
--- Comment #5 from Austin English austinenglish@gmail.com 2009-04-29 18:19:20 --- Mouse slipped...
http://bugs.winehq.org/show_bug.cgi?id=18283
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Austin English austinenglish@gmail.com 2009-04-29 18:19:36 --- Closing.