writing .scn file

[Gedare Bloom]

The .scn file is intended to be the "screen" output of the file. As we
now just get the terminal output directly, you can update the .scn
file to be the output you capture from the terminal  (prior to FATAL).
I don't think anyone is actually comparing these .scn files anymore,
they are mostly of historical significance.

On Wed, Apr 29, 2020 at 3:40 PM Eshan Dhawan <eshandhawan51 at gmail.com> wrote:
>
> Hello everyone,
> As I changed the test framework in the
> patch: https://lists.rtems.org/pipermail/devel/2020-April/059466.html
> to the new T_TEST framework
> and after running the test I got the output
>
> *** BEGIN OF TEST PSXGETCPUCLOCKID 1 ***
> *** TEST VERSION: 5.0.0.0c28e4e8f2768fd3cac0e7721d6f48776bbfd9e1-modified
> *** TEST STATE: EXPECTED_PASS
> *** TEST BUILD: RTEMS_POSIX_API
> *** TEST TOOLS: 9.3.0 20200312 (RTEMS 5, RSB 5 (78c6e159d467), Newlib 7947581)
> A:psxgetcpuclockid1
> S:Platform:RTEMS
> S:Compiler:9.3.0 20200312 (RTEMS 5, RSB 5 (78c6e159d467), Newlib 7947581)
> S:Version:5.0.0.0c28e4e8f2768fd3cac0e7721d6f48776bbfd9e1-modified
> S:BSP:rv32imac
> S:RTEMS_DEBUG:0
> S:RTEMS_MULTIPROCESSING:0
> S:RTEMS_POSIX_API:1
> S:RTEMS_PROFILING:0
> S:RTEMS_SMP:0
> B:pthread_getcpuclockid
> F:*:0::init.c:124:-1 == 0, EINVAL
> F:*:0::init.c:145:-1 == 0, EINVAL
> F:*:0::init.c:157:1 == 0, EINVAL
> F:*:0::init.c:172:3 == -1, EINVAL == ESRCH
> E:pthread_getcpuclockid:N:0:F:4:D:0.502748
> Z:psxgetcpuclockid1:C:1:N:0:F:4:D:0.503422
> Y:ReportHash:SHA256:aa6c4c5af8748cd4750ecc7c1215deaf22cb97825ab5a61be353ca3a8e44260d
>
> *** FATAL ***
> fatal source: 5 (RTEMS_FATAL_SOURCE_EXIT)
> fatal code: 0 (0x00000000)
> RTEMS version: 5.0.0.0c28e4e8f2768fd3cac0e7721d6f48776bbfd9e1-modified
> RTEMS tools: 9.3.0 20200312 (RTEMS 5, RSB 5 (78c6e159d467), Newlib 7947581)
> executing thread ID: 0x08b010001
> executing thread name:
>
> Now what do I add in the .scn file?
>
> Thanks
> - Eshan
>