if port collision is detected use lsof to check what is running there

[Tofel]

We want to discover what is causing these intermittent failures in CI:

Error: failed to setup test environment: failed to start chip router: 
start container: container start: Error response from daemon: 
failed to set up container networking: 
driver failed programming external connectivity on endpoint chip-router-ab0bb (5b2409a1b1a565e38e9a367f2c088bd158089e2c62cb82c73612f509446db9bc): 
failed to bind host port for 0.0.0.0:50050:172.18.0.2:50050/tcp: address already in use

[github-actions]

I see you updated files related to core. Please run make gocs in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[Copilot]

Pull request overview

Risk Rating: LOW (change is limited to error-path diagnostics, but it currently risks masking the original failure)

This PR adds extra diagnostics to the CRE CLI environment startup so that when a CI failure occurs due to a host port collision (“address already in use”), it attempts to run lsof to identify what process is using the conflicting port.

Changes:

• Add a helper (describePortUsage) that runs lsof for a given TCP port and returns its output.
• On setup failure containing “address already in use”, extract the port from the error string and print the lsof results.

Scrupulous human review suggested (high impact on debuggability of CI failures):

• The new “address already in use” error-handling path in StartCLIEnvironment, specifically how failures from lsof are handled (to avoid masking the original setup error) and how the port is parsed (to avoid panics / misleading errors).
• The lsof invocation behavior (timeouts, availability on runners, and filtering to relevant socket state).

[cl-sonarqube-production]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube