1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
This directory contains a battery of tests that exercise all the
functionality of ACE on Win32 and UNIX. These tests can be executed
in a single pass via a shell script run_tests.sh (on UNIX) or a batch
file run_tests.bat (on Win32).
We had problems running the batch file on Windows 95 and Windows NT
using the native DOS prompt. However we were able to get around this
problem by using a program called "4DOS for Windows NT" which also
displays a DOS prompt but allows us to run batch files through it.
The tests have been run on UNIX, Windows NT, and Windows 95 and they
all work with the following exceptions:
1. Name_Server_Test on Windows 95: this does not work on Windows 95
since Windows 95 has a different model for shared memory and does
not support explicitly selecting shared memory addresses.
2. UPIPE_Test and SPIPE_Test on Windows 95: these do not work on
Windows 95 since Windows 95 does not support the server side
functionality of accepting connections from clients using named pipes.
3. Proactor_Test (to be added) on Windows 95: this does not work on
Windows 95 since Windows 95 does not support I/O completion ports.
Notes:
1. Each test creates a log file and writes it to the ./log/
directory. The log directory can be changed in the test_config.h
file.
2. Each log file contains a time stamp of when the test began and also
a time stamp indicating when the test ended. If the ending time stamp
is missing, you can assume that the test did not succeed.
3. None of the tests require any command line parameters. This is in
accordance with the keeping the test-suite a "one-button" test. If
any of the tests require any variable parameters these are
specified in test_config.h.
4. Time_Service_Test executes the Time Server and Clerk components
as two processes and so the executable "main" need to be present in the
netsvcs/bin directory. These components rely on config files. Two
sample config files are also present in the test-suite, namely
UNIXserver.conf and UNIXclerk.conf (and for Win32, Win32server.conf
and Win32clerk.conf).
On VxWorks, there currently is no batch file for running all of the
tests. If you would like to contribute one, that would be great.
The straightforward approach of loading a test program, running it
by calling ace_main, and then unloading it doesn't work, because
the unload often fails. If the program is run by spawning a new
task (-> sp ace_main), then the unload will succeed. However, then
we need a way to tell when the test is done. OS::thr_join () could
probably be used, but it first has to be implemented for VxWorks.
As of ACE 4.3, all of the tests on g++ 2.7.2/VxWorks 5.3.1 pass, with
these exceptions:
Buffer_Stream_Test ENOTSUP: unknown
Conn_Test unknown
MM_Shared_Memory_Test ENOTSUP: unknown
Mem_Map_Test ENOTSUP: unknown (mmap)
Naming_Test failed: (uses mmap?)
Pipe_Test failed: fork
Process_Mutex_Test (not run: requires processes)
Process_Strategy_Test (not run: requires processes)
Reactor_Notify_Test unknown
SPIPE_Test ENOTSUP: ace_pipe_name not found
Service_Config_Test failed: page fault
Sigset_Ops_Test failed: line 109 assertion
Time_Service_Test failed: uses spawn (fork)
Tokens_Test (not run: uses fork)
If you are able to determine the cause of failure of Conn_Test or
Reactor_Test, please let us know! The other tests need to be fixed
so that they fail gracefully on VxWorks.
If you have any questions/suggestions, please send email to
ace-users@cs.wustl.edu.
|
