| commit | cf35500db2b4cadf91e56a2e85c227fe683ad705 | [log] [tgz] |
|---|---|---|
| author | Tomáš Pecka <tomas.pecka@cesnet.cz> | Wed May 17 11:40:30 2023 +0200 |
| committer | Tomáš Pecka <tomas.pecka@cesnet.cz> | Fri May 19 12:20:18 2023 +0200 |
| tree | 67a4ea24b9720fc61a47ca0471240951d998854d | |
| parent | be858e23dbb91bcf18f6fcf9386653e4eb18bf3a [diff] |
tests: explicitely call optional<T>::has_value in dataFromSysrepo
In dateFromSysrepo test function we check if getData return value
(std::optional) actually has value by calling REQUIRE(data).
However, if the std::optional does not have value and the REQUIRE fails
something like this gets printed:
velia/tests/test_sysrepo_helpers.h:21: FATAL ERROR: REQUIRE( data ) is NOT correct!
values: REQUIRE( {?} )
That is because doctest does not know how to print instances of
std::optional. A minor change to the REQUIRE expression seems like a
better idea than performing some template magic to allow doctest to
start printing std::optional objects.
And now the message shows a less confusing message (at least for me).
velia/tests/test_sysrepo_helpers.h:21: FATAL ERROR: REQUIRE( data.has_value() ) is NOT correct!
values: REQUIRE( false )
Change-Id: Id6f02f9efea1338328b4a53540296e012c6e573d
Together with sysrepo, this software provides "general system management" of embedded devices. The target platform is anything that runs Linux with systemd. This runs in production on CzechLight SDN DWDM devices.
This component tracks the overal health state of the system, including various sensors, or the state of systemd units. As an operator-friendly LED at the front panel of the appliance shows the aggregated health state.
Firmware can be updated via RAUC, and various aspects of the system's configuration can be adjusted. This includes a firewall, basic network settings, and authentication management.
For a full list, consult the yang/ directory in this repository.
ietf-access-control-list, RFC 8519 (with deviations)ietf-hardware, RFC 8348ietf-system, RFC 7317 (partial support)ietf-interfaces, RFC 8343 (generating config for systemd-networkd, with extensions)ietf-routing, RFC 8349 (see above)czechlight-system