TEST BRANCH [DO NOT MERGE]

[adamdebek]

Description

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

How Has This Been Tested?

• Already covered by automatic testing.
• New test added: (add PR link here).
• Tested by hand on: (list targets here).

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing linter checks and tests passed.
• My changes generate no new compilation warnings for any of the targets.

Special treatment

• This PR needs additional PRs to work (list the PRs, preferably in merge-order).
• I will merge this PR by myself when appropriate.

[github-actions]

Unit Test Results

6 580 tests   5 951 ✅  34m 39s ⏱️
  368 suites    626 💤
    1 files        3 ❌

For more details on these failures, see this check.

Results for commit 490e4a8.

♻️ This comment has been updated with latest results.

[github-actions]

[clang-format-pr] _{reported by reviewdog 🐶}
suggested fix

Suggested change

	#define LWIP_DEBUG 1
	#define TCP_DEBUG LWIP_DBG_ON
	#define LWIP_DEBUG 1
	#define TCP_DEBUG LWIP_DBG_ON