Error running analysis for cpp: Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.20.0/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 Instruction::StoreInstruction#ae96f30c/1@660a2emi Severe disk cache trouble (corruption or out of space) at /home/runner/work/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/5d.pack: Failed to write item to disk The RA to evaluate was: {1} r1 = JOIN num#Opcode::TStore#1b6ec668 WITH `SSAConstruction::getInstructionOpcode/2#3bb281a5` ON FIRST 1 OUTPUT Rhs.1 {1} | JOIN WITH Instruction::CopyInstruction#9aba5cb5 ON FIRST 1 OUTPUT Lhs.0 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:136) 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:707) 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/5d.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.writers.IntArrayWriter.increaseCapacity(IntArrayWriter.java:205) at com.semmle.inmemory.relations.writers.UnsortedRelationWriter.increaseArrayCapacity(UnsortedRelationWriter.java:153) at com.semmle.inmemory.relations.writers.UnsortedRelationWriter.makeSpaceIfNeeded(UnsortedRelationWriter.java:136) at com.semmle.inmemory.relations.writers.UnsortedRelationWriter$1.addBatch(UnsortedRelationWriter.java:115) at com.semmle.inmemory.pipeline.RelationWritingStep$RelationWritingState.processBatch(RelationWritingStep.java:90) at com.semmle.inmemory.pipeline.SimpleStep$SimpleState.deliverBatch(SimpleStep.java:146) at com.semmle.inmemory.pipeline.TuplePickerStep$TuplePickerState.deliverSubset(TuplePickerStep.java:155) at com.semmle.inmemory.pipeline.SetOpStep$SetOpState.processBatch(SetOpStep.java:76) at com.semmle.inmemory.pipeline.SimpleStep$SimpleState.deliverBatch(SimpleStep.java:146) at com.semmle.inmemory.pipeline.SimpleStep$SimpleState.deliverOwnBatch(Si

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636