Skip to content

Expect the intervehicle report on vehicle2's intervehicle layer - #60

Merged
tsaubergine merged 1 commit into
mainfrom
intervehicle-test-layer
Nov 12, 2026
Merged

tsaubergine merged 1 commit into
mainfrom
intervehicle-test-layer

Conversation

@tsaubergine

Copy link
Copy Markdown
Member

Summary

test/intervehicle/basic.test.yml used to check vehicle2 by looking for raw DCCLForwardedData on gobyd's internal goby::middleware::intervehicle::modem_data_in group, matching on the DCCL id in the first frame. Now vehicle2's endpoint is a LAYER_INTERVEHICLE endpoint. Like the example's subscriber, it subscribes to dccl.NavigationReport on the broadcast group ("0") from modem 1, and the expectation checks the decoded report (z <= 0). vehicle1's check, the outgoing report on its interprocess layer, is unchanged.

test/README.md's table entry is updated to match.

Dependencies

This uses goby test's intervehicle endpoints, which are already in goby3's 3.0 branch. It doesn't depend on the goby interface PRs.

Test plan

  • ctest -R goby3_example_test_basic_intervehicle passes; veh2 receives the report across the UDP multicast link.
  • goby3_example_validate_basic_intervehicle passes.
  • Negative check: with the condition changed to z > 0, the step fails. It received 4 decoded reports and rejected each (z GT 0: got -303), which shows the expectation is checking real reports from vehicle1.

Generated by Claude Code

The basic intervehicle harness checked vehicle2 for raw DCCLForwardedData
on gobyd's internal modem_data_in group. vehicle2's endpoint is now on
the intervehicle layer: as the example's subscriber does, it subscribes
to dccl.NavigationReport on the broadcast group from modem 1 and checks
the decoded report.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01TCmHEtuYatVV6nSaJPTa6z
@tsaubergine
tsaubergine merged commit a29c507 into main Nov 12, 2026
5 checks passed
@tsaubergine
tsaubergine deleted the intervehicle-test-layer branch November 12, 2026 04:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants