failed to resolve address for github.com

I am repeatedly getting the following error: https://github.com/comit-network/comit-rs/pull/2496/checks?check_run_id=603879402

The machine running the action is not able to resolve github.com.

Has anyone encountered and resolve the same error?

Updating crates.io index
warning: spurious network error (2 tries remaining): failed to resolve address for github.com: nodename nor servname provided, or not known; class=Net (12)
warning: spurious network error (1 tries remaining): failed to resolve address for github.com: nodename nor servname provided, or not known; class=Net (12)
error: failed to fetch `https://github.com/rust-lang/crates.io-index`

Caused by:
  failed to resolve address for github.com: nodename nor servname provided, or not known; class=Net (12)
make: *** [build] Error 101
##[error]Process completed with exit code 2.

@d4nte ,

From the link you shared, I did not find any failed job or step, and also did not find the error messages you mentioned from the workflow runs for the PR. Please clearly indicate which jobs or steps have the problem in the workflow, so that we can check the detailed related configurations in your workflow to analyze the root cause.

In addition, you seem have not enabled debug logging in your repository, maybe you can try enabling debug logging to see if you can get more detailed debug logs when some jobs or steps have problems in the workflow runs.
To enable debug logging, you can add " ACTIONS_RUNNER_DEBUG" and " ACTIONS_STEP_DEBUG" as secrets in the repository and set their values to be " true". After that, you can re-run the failed workflow run or trigger a new run to view the debug logs.

Hi @brightran ,

Hopefully this link should work: https://github.com/comit-network/comit-rs/runs/603879402?check_suite_focus=true

@d4nte ,

Please check with the below steps:

  1. Run make build command with the same project on your local machine to see if have the same problem.

  2. Set the option jobs.<job_id>.strategy.fail-fast to be false , to see if the same problem also occurs on Windows runner and Linux runner.

In addition, here has an earlier reported issue ticket (rust-lang/cargo #2637) for the similar problem, looks like this is a legacy issue.