Error running analysis for cpp: Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.18.2/x64/codeql/codeql database run-queries --ram=14567 --threads=4 /home/runner/work/_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 _IRFunction::IRFunction.getEntryBlock/0#a456a266_SSAConstruction::hasInstruction/1#7cdd58bd__IRBlock__#shared/7@a1f5b27o Severe disk cache trouble (corruption or out of space) at /home/runner/work/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/b7/0a.pack: Failed to write item to disk The RA to evaluate was: {6} r1 = JOIN `_IRBlock::Cached::MkIRBlock#ca79450a_10#join_rhs_IRBlock::Cached::getInstruction/2#b0d4a3ea_Operand:__#shared` WITH `SSAConstruction::hasInstruction/1#7cdd58bd` ON FIRST 1 OUTPUT Lhs.5, Lhs.2, Lhs.1, Lhs.3, Lhs.4, Lhs.0 {7} | JOIN WITH `IRFunction::IRFunction.getEntryBlock/0#a456a266` ON FIRST 2 OUTPUT Lhs.1, Lhs.2, Lhs.1, Lhs.3, Lhs.4, Lhs.0, Lhs.5 return r1 (eventual cause: IOException "No space left on device") at com.semmle.inmemory.pipeline.PipelineInstance.wrapWithRaDump(PipelineInstance.java:168) at com.semmle.inmemory.pipeline.PipelineInstance.exceptionCaught(PipelineInstance.java:152) 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:93) 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 /home/runner/work/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/b7/0a.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:340) at com.semmle.inmemory.alloc.RigidArrayAllocator.allocateArrays(RigidArrayAllocator.java:178) at com.semmle.inmemory.alloc.MemoryManager.allocateArrays(MemoryManager.java:411) at com.semmle.inmemory.relations.IntArraySorter.sortAndDeliverCompletePages(IntArraySorter.java:167) at com.semmle.inmemory.relations.writers.IntArrayWriter.sortAndDeliverCompletePages(IntArrayWriter.java:252) at com.semmle.inmemory.relations.writers.UnsortedRelationWriter.makeSpaceIfNeeded(UnsortedRelationWriter.java:135) at com.semmle.inmemory.relations.writers.UnsortedRelationWriter$1.addBatch(UnsortedRelationWriter.java:117) at com.semmle.inmemory.pipeline.RelationWritingStep$RelationWritingState.processBatch(RelationWritingStep.java:84) 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.TuplePicke

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache/restore@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

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