Skip to content

build: change: run the protocol tests with opp_repl - #1375

Merged
levy merged 2 commits into
masterfrom
topic/tests-on-opp-repl-protocol
Oct 27, 2026
Merged

levy merged 2 commits into
masterfrom
topic/tests-on-opp-repl-protocol

Conversation

@levy

@levy levy commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

The protocol workflow still runs inet_run_protocol_tests, which uses INET's own copy of opp_repl's test framework in python/inet. The two copies drift, so a developer who runs a protocol test with opp_repl and the CI job can select different tests. This pull request is the second of the series that #1373 started (plan: plan/pending/tests-on-opp-repl.md), and it moves the protocol workflow to opp_repl.

The workflow now installs opp_repl from its github_ci branch, with pyyaml for inet-gpl's packetdrill suite, and runs opp_run_protocol_tests --load $INET_ROOT -p inet. INET's inet.opp from #1373 gives the suites of tests/protocol, the shared tests/protocol/lib and the debug mode. The inet-gpl build and the packetdrill check stay. Nothing changes in the tests or their expected results.

Commits, in reading order

  • 512db34 build: change: run the protocol tests with opp_repl
  • f808a9e plan: change: record step S2 of the tests on opp_repl

Evidence

  • In a podman copy of the GitHub job (ubuntu 24.04, clang 16) on one debug build, with inet-gpl at d276352, the old and the new runner give the same verdict for each of the 824 protocol tests: 394 PASS, 50 expected FAIL and 379 unexpected FAIL. Of the unexpected failures, 303 are packetdrill wrappers (tcp/linux 157, tcp/packetdrill 146) and 76 are standards tests (mld 25, igmp 17, nd 15, rip 10, ipv6 9).
  • The packetdrill check fails there with INET_CRASH (two unused configuration entries).

Not verified: the GitHub runners. On master, the packetdrill check fails and stops the job before the protocol tests (run 40334828231), so a run of this branch also stops there. The repair of the check is not a part of this series.

🤖 Generated with Claude Code

levy added 2 commits October 26, 2026 16:40
The protocol workflow ran inet_run_protocol_tests, which uses INET's own copy of opp_repl's test framework in python/inet; the two copies drift.

The workflow now installs opp_repl from its github_ci branch, with pyyaml for inet-gpl's packetdrill suite, and runs opp_run_protocol_tests --load $INET_ROOT -p inet. INET's inet.opp gives the suites of tests/protocol, the shared tests/protocol/lib and the debug mode. The inet-gpl build and the packetdrill check stay: inet_run_packetdrill is INET's own tool, and the check keeps a broken inet-gpl from turning the packetdrill wrappers into skips.

Checked in the GitHub-job container on one debug build, with inet-gpl at d276352: both runners give the same verdict for each of the 824 protocol tests (394 PASS, 50 expected FAIL, 379 unexpected FAIL). The packetdrill check fails there with INET_CRASH (two unused configuration entries), and it also fails on GitHub master before the protocol tests run, so the unexpected failures do not come from this change.

Plan: plan/pending/tests-on-opp-repl.md

Change: build | behavior.change | - | tests-on-opp-repl
The protocol workflow runs opp_run_protocol_tests, and both runners give the same verdict for each protocol test. The plan records the check and a finding: the packetdrill check fails on master before the protocol tests run.

Plan: plan/pending/tests-on-opp-repl.md

Change: plan | behavior.change | - | tests-on-opp-repl
@levy
levy force-pushed the topic/tests-on-opp-repl-protocol branch from 5c5bfbb to f808a9e Compare October 26, 2026 15:59
@levy
levy changed the base branch from topic/tests-on-opp-repl to master October 26, 2026 15:59
@levy
levy merged commit 8ef7349 into master Oct 27, 2026
4 of 5 checks passed
@levy
levy deleted the topic/tests-on-opp-repl-protocol branch October 27, 2026 10:02
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.

1 participant