The submit composite action used nc (netcat) to check if the Testflinger server was listening at the appropriate port. This was a simple test that often failed to detect connectivity issues that would later cause the submit action to fail (e.g. proxy problems), partly because nc operates at a lower protocol level (TCP) than the actual HTTPS Testflinger requests.
In this PR, the nc test is replaced by a more refined one that uses curl to check if an HTTPS connection can be established with the Testflinger server.
Documentation
No changes to the documentation are required.
Tests
The action was tested:
in a workflow executing on a self-hosted Github runner with proxy-related connectivity issues (sample run).
in a workflow executing a self-hosted Github runner with no connectivity issues (sample run).
I updated the PR, adding the verbose option and also capturing standard error to a file, so that the diagnostics are only displayed in case of an issue.
Description
The
submit
composite action usednc
(netcat) to check if the Testflinger server was listening at the appropriate port. This was a simple test that often failed to detect connectivity issues that would later cause thesubmit
action to fail (e.g. proxy problems), partly becausenc
operates at a lower protocol level (TCP) than the actual HTTPS Testflinger requests.In this PR, the
nc
test is replaced by a more refined one that usescurl
to check if an HTTPS connection can be established with the Testflinger server.Documentation
No changes to the documentation are required.
Tests
The action was tested: