summaryrefslogtreecommitdiff
path: root/tests
diff options
context:
space:
mode:
authorlevine <levine@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1997-09-08 15:56:00 +0000
committerlevine <levine@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1997-09-08 15:56:00 +0000
commit73c9aa508eba6a60615475ba76d78222eec004dc (patch)
tree358907c94f11b8321be8938c0f49ef3257574eba /tests
parent23a331ea4f9dc51d33c9318e2113c8330eb121c5 (diff)
downloadATCD-73c9aa508eba6a60615475ba76d78222eec004dc.tar.gz
updated VxWorks status
Diffstat (limited to 'tests')
-rw-r--r--tests/README17
1 files changed, 5 insertions, 12 deletions
diff --git a/tests/README b/tests/README
index 68343722db7..a826a2e9bc2 100644
--- a/tests/README
+++ b/tests/README
@@ -45,15 +45,6 @@ Notes:
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:
@@ -61,18 +52,20 @@ these exceptions:
Conn_Test unknown
MM_Shared_Memory_Test ENOTSUP: unknown
Mem_Map_Test ENOTSUP: unknown (mmap)
+ Mutex_Test ENOTSUP: unknown
Naming_Test failed: (uses mmap?)
Pipe_Test failed: requires fork
Process_Mutex_Test failed: requires fork
Process_Strategy_Test failed: /tmp/ace_temp_file not founc
+ Reactors_Test failed: problem with test?
Reactor_Notify_Test unknown
Service_Config_Test failed: page fault
Time_Service_Test failed: requires fork
Tokens_Test failed: unknown
-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 are able to determine the cause of failure of Conn_Test,
+Mutex_Test, or Reactors_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