> On Sep 22, 2019, at 18:45 , Chris Johns wrote:
>
> On 23/9/19 12:33 am, dufa...@hda.com wrote:
>>> On Sep 22, 2019, at 07:12 , wrote:
On Sep 21, 2019, at 17:29 , dufa...@hda.com wrote:
> On Sep 21, 2019, at 17:04 , Chris Johns wrote:
>>> (…)
> The tester is designed to avoid
On 23/9/19 12:33 am, dufa...@hda.com wrote:
>> On Sep 22, 2019, at 07:12 , wrote:
>>> On Sep 21, 2019, at 17:29 , dufa...@hda.com wrote:
On Sep 21, 2019, at 17:04 , Chris Johns wrote:
>> (…)
The tester is designed to avoid cycling power. A clean working target
should
only
> On Sep 22, 2019, at 07:12 , wrote:
>
>
>
>> On Sep 21, 2019, at 17:29 , dufa...@hda.com wrote:
>>
>>
>>
>>> On Sep 21, 2019, at 17:04 , Chris Johns wrote:
>>>
>>>
> (…)
>>> The tester is designed to avoid cycling power. A clean working target should
>>> only need a single power on
> On Sep 21, 2019, at 17:29 , dufa...@hda.com wrote:
>
>
>
>> On Sep 21, 2019, at 17:04 , Chris Johns wrote:
>>
>>
(…)
>> The tester is designed to avoid cycling power. A clean working target should
>> only need a single power on at the start and a single power off at the end.
>> Repeated
> On Sep 21, 2019, at 17:04 , Chris Johns wrote:
>
> On 22/9/19 2:39 am, dufa...@hda.com wrote:
>>> On Sep 21, 2019, at 11:44 , Joel Sherrill wrote:
>>> On Sat, Sep 21, 2019, 10:09 AM Peter Dufault wrote:
>>> Most of the failures I see on “beatnik” are detected by
>>> “rtems_test_assert()”.
On 22/9/19 2:39 am, dufa...@hda.com wrote:
>> On Sep 21, 2019, at 11:44 , Joel Sherrill wrote:
>> On Sat, Sep 21, 2019, 10:09 AM Peter Dufault wrote:
>> Most of the failures I see on “beatnik” are detected by
>> “rtems_test_assert()”. That prints the assertion and calls exit, e.g. on
>>
> On Sep 21, 2019, at 11:44 , Joel Sherrill wrote:
>
>
>
> On Sat, Sep 21, 2019, 10:09 AM Peter Dufault wrote:
> Most of the failures I see on “beatnik” are detected by
> “rtems_test_assert()”. That prints the assertion and calls exit, e.g. on
> beatnik:
>
> ] allocate most of memory -
On Sat, Sep 21, 2019, 10:09 AM Peter Dufault wrote:
> Most of the failures I see on “beatnik” are detected by
> “rtems_test_assert()”. That prints the assertion and calls exit, e.g. on
> beatnik:
>
> ] allocate most of memory - attempt to fail chroot - expect ENOMEM
> ]
>
Most of the failures I see on “beatnik” are detected by “rtems_test_assert()”.
That prints the assertion and calls exit, e.g. on beatnik:
] allocate most of memory - attempt to fail chroot - expect ENOMEM
] ../../../../../../rtems/c/src/../../testsuites/psxtests/psxchroot01/test.c:
126 status
