tests: Verify build fails with mismatched byte order
authorErica Bugden <ebugden@efficios.com>
Thu, 25 May 2023 20:16:44 +0000 (16:16 -0400)
committerErica Bugden <ebugden@efficios.com>
Tue, 20 Jun 2023 20:14:45 +0000 (16:14 -0400)
commit1d62391a8cfa56ab95059da56ce876f289566a9f
tree1c4e78bf85c2fe4e908698f2f4580f7cbd42b22e
parent9e49badc720f13957c3b47d7aea6f54092b1dd7a
tests: Verify build fails with mismatched byte order

This tests the byte order check added in the previous commit `Check that
native byte orders match at compilation`.

Change `byte-order-yes.yaml`:

This test configuration now defines the tracer byte order with
`native-byte-order: big-endian` (instead of
`trace-byte-order: big-endian`) so that this configuration can be used
both for the configuration tests and for the new byte order check test.
The `native-byte-order` property is used so that the C preprocessor
check will be present in the generated C code. The byte order is set to
`big-endian` so that building the generated C will fail on a
little-endian system.

This change does not reduce the test coverage because:
    a. `byte-order-yes.yaml` still tests that using one of the two byte
       order properties is a valid configuration, and
    b. The `trace-byte-order` property is tested via
       `trace-byte-order-big-endian.yaml` in the tracing tests.

Change-Id: Ic2aa7bdc7e56881233efe2e25153dc4e65ba309a
Signed-off-by: Erica Bugden <ebugden@efficios.com>
tests/config/yaml/3/configs/pass/type/byte-order-yes.yaml
tests/config/yaml/3/test_fail_byte_order_check.py [new file with mode: 0644]
This page took 0.026283 seconds and 4 git commands to generate.