source: rtems/testsuites/libtests/rtems++/rtems++.scn @ d5154d0f

5
Last change on this file since d5154d0f was d5154d0f, checked in by Aun-Ali Zaidi <admin@…>, on Dec 23, 2015 at 8:44:02 PM

api: Remove deprecated Notepads

Notepads where a feature of RTEMS' tasks that simply functioned in
the same way as POSIX keys or threaded local storage (TLS). They were
introduced well before per task variables, which are also deprecated,
and were barely used in favor of their POSIX alternatives.

In addition to their scarce usage, Notepads took up unnecessary memory.
For each task:

  • 16 32-bit integers were allocated.
  • A total of 64 bytes per task per thread.

This is especially critical in low memory and safety-critical applications.

They are also defined as uint32_t, and therefore are not guaranteed to
hold a pointer.

Lastly, they are not portable solutions for SMP and uniprocessor systems,
like POSIX keys and TLS.

updates #2493.

  • Property mode set to 100644
File size: 8.2 KB
Line 
1
2
3*** RTEMS++ TEST ***
4INIT - Task.create() - RTEMS[19] invalid thread priority
5INIT - Task.create() - RTEMS[00] successful completion
6INIT - Task.create() - RTEMS[16] illegal on calling thread
7INIT - Task.restart() - RTEMS[14] thread is in wrong state
8INIT - Task.start(0xDEADDEAD) - RTEMS[00] successful completion
9INIT - Destroy it's self
10<pause - screen 1>
11 START Task Class test
12TA1  - test argument - argument matched
13TA1  - copy constructor - local and this id's match
14TA1  - copy constructor - local and this name's match
15TA1  - copy operator - local and this id's match
16TA1  - copy operator - local and this name's match
17TA1  - not owner destroy's task - RTEMS[23] not owner of resource
18TA1  - connect to a local valid task name - RTEMS[00] successful completion
19TA1  - connect to an invalid task name - RTEMS[03] invalid object name
20SELF - connect to a task on an invalid node - RTEMS[03] invalid object name
21TA1  - restart from a non-owner - RTEMS[23] not owner of resource
22<pause - screen 2>
23TA1  - wake after 0 secs - RTEMS[00] successful completion
24TA1  - wake after 500 msecs - RTEMS[00] successful completion
25TA1  - wake after 5 secs - RTEMS[00] successful completion
26TA1  - wake when - to do
27TA1  - connected object wake after 0 secs - RTEMS[00] successful completion
28TA1  - connected object wake after 500 msecs - RTEMS[00] successful completion
29TA1  - connected object wake after 5 secs - RTEMS[00] successful completion
30TA1  - connected object wake when - to do
31SELF - self object wake after 0 secs - RTEMS[00] successful completion
32SELF - self object wake after 500 msecs - RTEMS[00] successful completion
33SELF - self object wake after 5 secs - RTEMS[00] successful completion
34SELF - self object wake when - to do
35TA1  - get priority - RTEMS[00] successful completion, priority is 10
36TA1  - set priority to 512 - RTEMS[19] invalid thread priority
37TA1  - set priority to 25 - RTEMS[00] successful completion
38TA1  - set priority to original - RTEMS[00] successful completion, priority was 25
39TA1  - connected object get priority - RTEMS[00] successful completion, priority is 10
40TA1  - connected object set priority to 512 - RTEMS[19] invalid thread priority
41TA1  - connected object set priority to 25 - RTEMS[00] successful completion
42TA1  - connected object set priority to original - RTEMS[00] successful completion, priority was 25
43SELF - self object get priority - RTEMS[00] successful completion, priority is 10
44SELF - self object set priority to 512 - RTEMS[19] invalid thread priority
45SELF - self object set priority to 25 - RTEMS[00] successful completion
46SELF - self object set priority to original - RTEMS[00] successful completion, priority was 25
47 END Task Class test
48<pause - screen 3>
49 START TaskMode Class test
50SELF - get mode - RTEMS[00] successful completion,
51         mode is 0x00000500, RTEMS_NO_PREEMPT RTEMS_NO_TIMESLICE RTEMS_ASR INTMASK=0
52SELF - get preemption state - RTEMS[00] successful completion,
53         mode is 0x00000100, RTEMS_NO_PREEMPT
54SELF - set preemption state to RTEMS_PREEMPT - RTEMS[00] successful completion,
55         mode is 0x00000400, RTEMS_PREEMPT RTEMS_TIMESLICE RTEMS_ASR INTMASK=0
56SELF - set preemption state to RTEMS_NO_PREEMPT - RTEMS[00] successful completion,
57         mode is 0x00000500, RTEMS_NO_PREEMPT RTEMS_NO_TIMESLICE RTEMS_ASR INTMASK=0
58SELF - get timeslice state - RTEMS[00] successful completion,
59         mode is 0x00000000, RTEMS_TIMESLICE
60SELF - set timeslice state to RTEMS_TIMESLICE - RTEMS[00] successful completion,
61         mode is 0x00000700, RTEMS_NO_PREEMPT RTEMS_NO_TIMESLICE RTEMS_ASR INTMASK=0
62SELF - set timeslice state to RTEMS_NO_TIMESLICE - RTEMS[00] successful completion,
63         mode is 0x00000500, RTEMS_NO_PREEMPT RTEMS_NO_TIMESLICE RTEMS_ASR INTMASK=0
64SELF - get asr state - RTEMS[00] successful completion,
65         mode is 0x00000400, RTEMS_ASR
66SELF - set asr state to RTEMS_ASR - RTEMS[00] successful completion,
67         mode is 0x00000100, RTEMS_NO_PREEMPT RTEMS_NO_TIMESLICE RTEMS_NO_ASR INTMASK=0
68SELF - set asr state to RTEMS_NO_ASR - RTEMS[00] successful completion,
69         mode is 0x00000500, RTEMS_NO_PREEMPT RTEMS_NO_TIMESLICE RTEMS_ASR INTMASK=0
70SELF - get current interrupt level - RTEMS[00] successful completion, level is 0
71SELF - set interrupt level to 102 - RTEMS[00] successful completion
72SELF - set interrupt level to original level - RTEMS[00] successful completion, level was 6
73SELF - set mode to original mode - RTEMS[00] successful completion,
74         mode is 0x00000500, RTEMS_NO_PREEMPT RTEMS_NO_TIMESLICE RTEMS_ASR INTMASK=0
75 END TaskMode Class test
76<pause - screen 4>
77 START Event Class test
78TA1  - create task 2 - RTEMS[00] successful completion
79TA1  - start task 2 - RTEMS[00] successful completion
80TA1  - construct event connecting to task 2 - RTEMS[00] successful completion
81TA2  - event no wait - RTEMS[13] request not satisfied
82TA2  - event 5 secs timeout - RTEMS[06] timed out waiting
83TA2  - event wait forever for signal 0 from TA1 ....
84TA1  - send event signal 0 using the task id - RTEMS[00] successful completion
85TA2  - RTEMS[00] successful completion, signals out are 0x00000001
86TA2  - event wait forever for signal 0 from TA1 ....
87TA1  - send event signal 0 using the task object reference - RTEMS[00] successful completion
88TA2  - RTEMS[00] successful completion, signals out are 0x00000001
89TA2  - event wait forever for signal 31 from TA1 ....
90TA1  - send event signal 31 using connected id - RTEMS[00] successful completion
91TA2  - RTEMS[00] successful completion, signals out are 0x80000000
92TA2  - event wait forever for signal 0 and 31 from TA1 ....
93TA1  - send event signal 0 and 31 - RTEMS[00] successful completion
94TA1  - waiting 5 secs for TA2 to finish
95TA2  - RTEMS[00] successful completion, signals out are 0x80000001
96TA2  - send event signal 1 - RTEMS[00] successful completion
97TA2  - event wait forever for signal 1 from TA2 - RTEMS[00] successful completion, signals out are 0x00000002
98TA2  - destroy itself
99 END Event Class test
100<pause - screen 5>
101 START Interrupt Class test
102 do not know a portable BSP type interrupt test
103 END Interrupt Class test
104<pause - screen 6>
105 START MessageQueue Class test
106TA1  - construct message queue 1 with no memory error - RTEMS[13] request not satisfied
107TA1  - construct/create message queue 2 - RTEMS[00] successful completion
108TA1  - send u1 to mq_2 - RTEMS[00] successful completion
109TA1  - urgent send u2 to mq_2 - RTEMS[00] successful completion
110TA1  - create task 3_1 - RTEMS[00] successful completion
111TA1  - start task 3_1 - RTEMS[00] successful completion
112TA1  - create task 3_2 - RTEMS[00] successful completion
113TA1  - start task 3_2 - RTEMS[00] successful completion
114TA31 - construction connect mq_2 - RTEMS[00] successful completion
115TA31 - loopback from mq_2 to mq_2 ...
116TA31 - mq_2 receive - RTEMS[00] successful completion, size=12, message string size=11
117TA31 - loopback to mq_2 - RTEMS[00] successful completion
118TA32 - construction connect mq_2 - RTEMS[00] successful completion
119TA32 - loopback from mq_2 to mq_2 ...
120TA32 - mq_2 receive - RTEMS[00] successful completion, size=12, message string size=11
121TA32 - loopback to mq_2 - RTEMS[00] successful completion
122TA1  - receive u2 on mq_2 ...
123TA1  - RTEMS[00] successful completion
124TA1  - message u2 received correctly
125TA1  - receive u1 on mq_2 ...
126TA1  - RTEMS[00] successful completion
127TA1  - message u1 received correctly
128TA31 - loopback from mq_2 to mq_2 ...
129TA32 - loopback from mq_2 to mq_2 ...
130TA1  - broadcast send b1 ...
131TA1  - mq_2 broadcast send - RTEMS[00] successful completion, count=2
132TA31 - mq_2 receive - RTEMS[00] successful completion, size=18, message string size=17
133TA31 - loopback to mq_2 - RTEMS[00] successful completion
134TA31 - destroy itself
135TA32 - mq_2 receive - RTEMS[00] successful completion, size=18, message string size=17
136TA32 - loopback to mq_2 - RTEMS[00] successful completion
137TA32 - destroy itself
138TA1  - receive message b1 on mq_2 from TA31...
139TA1  - RTEMS[00] successful completion
140TA1  - message b1 received correctly
141TA1  - receive message b1 on mq_2 from TA31...
142TA1  - RTEMS[00] successful completion
143TA1  - message b1 received correctly
144TA1  - send f1 to mq_2 - RTEMS[00] successful completion
145TA1  - send f1 to mq_2 - RTEMS[00] successful completion
146TA1  - send f1 to mq_2 - RTEMS[00] successful completion
147TA1  - flush mq_2 - RTEMS[00] successful completion, flushed=3
148 END MessageQueue Class test
149*** END OF RTEMS++ TEST ***
Note: See TracBrowser for help on using the repository browser.