codeql-action: codeql-action/init@v2 makes Runner.Worker.exe crash causing stuck Initialize CodeQL Step

We have implemented codeql scans on all our repositories and it was passing.

Now suddenly, the Initialize CodeQL step (codeql-action/init@v2) is stuck without any failures. It was originally stuck only for Java, but now for csharp as well; it fails on most of our self hosted runners (Windows Server 2019)

On further debugging, I noticed that if I don’t refresh the github page once it is stuck, I can still see the logs,

They are-

E:\actions-runners\_work\_tool\CodeQL\2.14.0-v2.14.0\x64\codeql\codeql.exe database init --db-cluster E:\actions-runners\_work\_temp\codeql_databases --source-root=E:\actions-runners\_work\testrepo\testrepo --language=java --begin-tracing --trace-process-name=Runner.Worker.exe --codescanning-config=E:\actions-runners\_work\_temp\user-config.yaml --overwrite 
566Calculating baseline information in E:\actions-runners\_work\testrepo\testrepo 
567Calculated baseline information for languages: java, ruby, yaml (263ms). 
568Resolving extractor java. 
569Successfully loaded extractor Java (java) from E:\actions-runners\_work\_tool\CodeQL\2.14.0-v2.14.0\x64\codeql\java. 
570Created skeleton CodeQL database at E:\actions-runners\_work\_temp\codeql_databases\java. This in-progress database is ready to be populated by an extractor.

Moreover, this seems to happen because Runner.worker.exe on the server crashes on the last step

Runner logs:

INFO ProcessInvokerWrapper] STDOUT/STDERR stream read finished.
[2023-07-18 08:50:46Z INFO ProcessInvokerWrapper] STDOUT/STDERR stream read finished.
[2023-07-18 08:50:46Z INFO ProcessInvokerWrapper] Finished process 10064 with exit code -1073741819, and elapsed time 00:01:39.7536427.
[2023-07-18 08:50:46Z INFO JobDispatcher] Worker finished for job 250fb49c-554f-57c5-b7b1-9fca27013847. Code: -1073741819
[2023-07-18 08:50:46Z INFO JobDispatcher] Return code -1073741819 indicate worker encounter an unhandled exception or app crash, attach worker stdout/stderr to JobRequest result.
[2023-07-18 08:50:46Z INFO GitHubActionsService] Starting operation Location.GetConnectionData
[2023-07-18 08:50:46Z INFO GitHubActionsService] Finished operation Location.GetConnectionData
[2023-07-18 08:50:47Z INFO JobDispatcher] finish job request for job 250fb49c-554f-57c5-b7b1-9fca27013847 with result: Failed
[2023-07-18 08:50:47Z INFO Terminal] WRITE LINE: 2023-07-18 08:50:47Z: Job Analyze testorg/testrepo (java) completed with result: Failed

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 1
  • Comments: 16 (6 by maintainers)

Most upvoted comments

Thanks for the details. I’ve relayed these to the responsible engineering team.