Error running analysis for cpp: Encountered a fatal error while running "/__t/CodeQL/2.19.3/x64/codeql/codeql database run-queries --ram=14567 --threads=4 /__w/_temp/codeql_databases/cpp --expect-discarded-cache --min-disk-free=1024 -v --intra-layer-parallelism". Exit code was 100 and error was: Oops! A fatal internal error occurred. Details: com.semmle.util.exception.CatastrophicError: An error occurred while evaluating SSAConstruction::DefUse::hasDefinitionAtRank/5#542c3cfb/5@8004f878 Severe disk cache trouble (corruption or out of space) at /__w/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/1b.pack: Failed to write item to disk The RA to evaluate was: {4} r1 = SCAN `SSAConstruction::DefUse::hasDefinition/4#7de389e1` OUTPUT In.0, In.2, In.3, In.1 {5} | JOIN WITH `SSAConstruction::DefUse::defUseRank/4#b00da839_0132#join_rhs` ON FIRST 3 OUTPUT Lhs.0, Lhs.3, Lhs.1, Rhs.3, Lhs.2 return r1 (eventual cause: IOException "No space left on device") at com.semmle.inmemory.pipeline.MetaPipelineInstance.wrapWithRaDump(MetaPipelineInstance.java:204) at com.semmle.inmemory.pipeline.MetaPipelineInstance.exceptionCaught(MetaPipelineInstance.java:174) at com.semmle.inmemory.scheduler.execution.ThreadableWork.handleAndLog(ThreadableWork.java:593) at com.semmle.inmemory.scheduler.execution.ThreadableWork.doSomeWork(ThreadableWork.java:410) at com.semmle.inmemory.scheduler.IntensionalLayer$IntensionalWork.evaluate(IntensionalLayer.java:132) at com.semmle.inmemory.scheduler.SimpleLayerTask$SimpleLayerWork.doWork(SimpleLayerTask.java:69) at com.semmle.inmemory.scheduler.execution.ThreadableWork.doSomeWork(ThreadableWork.java:396) at com.semmle.inmemory.scheduler.execution.ExecutionScheduler.runnerMain(ExecutionScheduler.java:677) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source) Caused by: Severe disk cache trouble (corruption or out of space) at /__w/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/1b.pack: Failed to write item to disk (eventual cause: IOException "No space left on device") at com.semmle.inmemory.caching.RelationCacheImpl.lambda$create$0(RelationCacheImpl.java:87) at com.semmle.inmemory.caching.byhash.disk.OnDiskStore.put(OnDiskStore.java:136) at com.semmle.inmemory.caching.byhash.interfaces.HashBasedCache.putIfPresent(HashBasedCache.java:29) at com.semmle.inmemory.caching.byhash.evict.Evictor$ItemHandle.writeToDisk(Evictor.java:723) at java.base/java.util.ArrayList.forEach(Unknown Source) at com.semmle.inmemory.caching.byhash.evict.Evictor.writeSelectedItems(Evictor.java:1059) at com.semmle.inmemory.caching.byhash.evict.Evictor.reduceMemoryUsage(Evictor.java:459) at com.semmle.inmemory.alloc.MemoryManager.reduceArraySpace(MemoryManager.java:342) at com.semmle.inmemory.alloc.RigidArrayAllocator.allocateArrays(RigidArrayAllocator.java:178) at com.semmle.inmemory.alloc.MemoryManager.allocateArrays(MemoryManager.java:413) at com.semmle.inmemory.relations.IntArraySorter.deliverAndWriteSortedTuples(IntArraySorter.java:350) at com.semmle.inmemory.relations.IntArraySorter.sortAndDeliverCompletePages(IntArraySorter.java:143) at com.semmle.inmemory.relations.writers.IntArrayWriter.sortAndDeliverCompletePages(IntArrayWriter.java:277) at com.semmle.inmemory.relations.writers.UnsortedRelationWriter.makeSpaceIfNeeded(UnsortedRelationWriter.java:133) at com.semmle.inmemory.relations.writers.UnsortedRelationWriter$1.addBatch(UnsortedRelationWriter.java:115) at com.semmle.inmemory.pipeline.RelationWritingStep$RelationWritingState.processBatch(RelationWritingStep.java:91) at com.semmle.inmemory.pipeline.SimpleStep$SimpleState.deliverBatch(SimpleStep.java:146) at com.semmle.inmemory.pipeline.SimpleStep$SimpleState.deliverOwnBatch(SimpleStep.java:130) at com.semmle.inmemory.pipeline.SimpleStep$SimpleState.getOutputBatch(SimpleStep.java:83) at com.semmle.inmemory.pipeline.ExpanderStep$ExpanderState.nextOutputBatch(ExpanderStep

Resource not accessible by integration

CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/

The Actions runner is running low on disk space (0.2398 GB available).

Resource not accessible by integration

The following actions use a deprecated Node.js version and will be forced to run on node20: pyTooling/Actions/with-post-step@v0.4.5, github/codeql-action/analyze@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 59 MB

Resource not accessible by integration

`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'

Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

Resource not accessible by integration

This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration

Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.19.3.