On 22/01/2018 20:07, Sebastian Huber wrote:
> On 21/01/18 22:39, Chris Johns wrote:
>>> This makes it easier to get the connection from the test output to the RTEMS
>>> build options.
>>>
>> Does rtems-test need to be updated?
>
> The rtems-test program seems to not care about a particular TEST_BU
On 21/01/18 22:39, Chris Johns wrote:
This makes it easier to get the connection from the test output to the RTEMS
build options.
Does rtems-test need to be updated?
The rtems-test program seems to not care about a particular TEST_BUILD
content:
https://lists.rtems.org/pipermail/build/2018
On 19/1/18 8:25 pm, Sebastian Huber wrote:
> Hello,
>
> the new test header is really great, e.g.
>
> *** BEGIN OF TEST BLOCK 8 ***
> *** TEST VERSION: 5.0.0.32d50688c655fbdc4cedcf9c06972b48e1ee498f
> *** TEST STATE: EXPECTED-PASS
> *** TEST BUILD: legacy-net
> *** TEST TOOLS: 7.2.0 20170814 (RTE
With the attached patch, the test header is now:
*** BEGIN OF TEST BLOCK 6 ***
*** TEST VERSION: 5.0.0.32d50688c655fbdc4cedcf9c06972b48e1ee498f-modified
*** TEST STATE: EXPECTED-PASS
*** TEST BUILD: RTEMS_DEBUG RTEMS_NETWORKING RTEMS_POSIX_API RTEMS_SMP
*** TEST TOOLS: 7.2.0 20170814 (RTEMS 5, RS