diff options
author | 2020-09-29 18:44:39 -0400 | |
---|---|---|
committer | 2020-09-29 18:55:53 -0400 | |
commit | 64092acda9a8581034c61732754eddee39f747ca (patch) | |
tree | 670c2c8f0cd47f0afcc931f1137483a2951b35ae /can-config-generator/build.sh | |
parent | 45514381c51ec65b1a2d05264a30a4d468348748 (diff) |
Update agl-vcar to match test expectationskoi_10.91.0koi/10.91.010.91.0
The regeneration of the agl-vcar and default plugin signals code
broke some expectations of the afb-test and pyagl tests, changes
to get things back to a good state:
- Add the missing J1939 messages that were in default-signals.cpp
before it was regenerated to the agl-vcar signals.json, and then
regenerate the affected cpp files; this fixes the J1939 test
expectations. An alternative approach would be using the ability
to load a different set of signals by configuring a different
plugin, but that has been deemed not workable for AGL CI.
- Remove the old application-generated.cpp file from the agl-vcar
examples directory to avoid confusion.
- Update the testFilter01pass.canreplay CAN data file used for the
Filter_Test_01/Step_2 test to use the non-FD version of the
0x3D9 CAN message that matches the agl-vcar definition. A new
0x3DA message that is a FD copy of 0x3D9 has been added to the
agl-vcar signals.json to allow testing CAN FD messaging, and a new
testFilter01pass-FD.canreplay data file has been added that can
potentially be used for doing so.
Bug-AGL: SPEC-3603
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Change-Id: I24c960ca33aaf122ac83a2583cb2df0cd6dbd9e3
Diffstat (limited to 'can-config-generator/build.sh')
0 files changed, 0 insertions, 0 deletions