Skip to content

CodeQL

CodeQL #400

Triggered via schedule August 22, 2024 05:06
Status Failure
Total duration 6h 2m 47s
Artifacts

codeql.yml

on: schedule
analyze  /  Build on Linux (gcc_debug)
3h 0m
analyze / Build on Linux (gcc_debug)
analyze  /  Build on Linux (fake, gcc_release, clang, simulated)
1h 8m
analyze / Build on Linux (fake, gcc_release, clang, simulated)
analyze  /  Build on Linux (python_lib)
25m 22s
analyze / Build on Linux (python_lib)
analyze  /  Build on Linux (python lighting-app)
5m 34s
analyze / Build on Linux (python lighting-app)
analyze  /  Build on Darwin (clang, python_lib, simulated)
6h 0m
analyze / Build on Darwin (clang, python_lib, simulated)
analyze  /  Build on Linux (coverage)
16m 28s
analyze / Build on Linux (coverage)
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 19 warnings
analyze / Build on Linux (fake, gcc_release, clang, simulated)
Process completed with exit code 1.
analyze / Build on Linux (gcc_debug)
Error running analysis for cpp: Encountered a fatal error while running "/__t/CodeQL/2.18.2/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 SsaInternalsCommon::isDef/6#c2f1b529/6@99fd146q Severe disk cache trouble (corruption or out of space) at /__w/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/bb/ce.pack: Failed to write item to disk The RA to evaluate was: {2} r1 = SCAN `CppType::CppType.hasUnspecifiedType/2#dispred#173eed9e` OUTPUT In.1, In.0 {2} | JOIN WITH `DataFlowPrivate::getMinIndirectionsForType/1#a7b686af` ON FIRST 1 OUTPUT Lhs.1, Rhs.1 {3} | JOIN WITH `SsaInternalsCommon::getLanguageType/1#9fd42135_10#join_rhs` ON FIRST 1 OUTPUT Lhs.0, Lhs.1, Rhs.1 {3} | JOIN WITH `SsaInternalsCommon::countIndirectionsForCppType/1#21060fdc` ON FIRST 1 OUTPUT Lhs.1, Lhs.2, Rhs.1 {4} | JOIN WITH PRIMITIVE range#bbf ON Lhs.0,Lhs.2 {3} | SCAN OUTPUT In.1, In.0, In.3 {5} | JOIN WITH `SsaInternalsCommon::isWrite/3#57164a14_102#join_rhs` ON FIRST 1 OUTPUT Lhs.0, Lhs.1, Lhs.2, Rhs.1, Rhs.2 {12} | JOIN WITH `SsaInternalsCommon::isDefImpl/4#ba239b5d` ON FIRST 1 OUTPUT bool _, Lhs.3, Lhs.0, Rhs.1, int _, int _, Lhs.4, Rhs.3, Rhs.2, Lhs.2, Lhs.1, int _ {6} | REWRITE WITH Out.0 := booleanAnd(In.6,In.7), Out.4 := (In.8 + In.9), Tmp.5 := (In.8 + In.9), Tmp.11 := (In.8 + In.10), Out.5 := (Tmp.5 - Tmp.11) KEEPING 6 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 /__w/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/bb/ce.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.RigidArrayAllocator$1.<init>(RigidArrayAllocator.java:216) at com.semmle.inmemory.alloc.RigidArrayAllocator.preallocate(RigidArrayAllocator.java:211) at com.semmle.inmemory.alloc.MemoryManager.preallocate(MemoryManager.java:489) at com.semmle.inmemory.caching.PagePrimitives.parseItem(PagePrimitives.java:91) at com.semml
analyze / Build on Darwin (clang, python_lib, simulated)
The job running on runner GitHub Actions 15 has exceeded the maximum execution time of 360 minutes.
analyze / Build on Darwin (clang, python_lib, simulated)
The operation was canceled.
analyze / Build on Linux (python lighting-app)
The following actions use a deprecated Node.js version and will be forced to run on node20: pyTooling/Actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
analyze / Build on Linux (python lighting-app)
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.
analyze / Build on Linux (python lighting-app)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
analyze / Build on Linux (coverage)
The following actions use a deprecated Node.js version and will be forced to run on node20: pyTooling/Actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
analyze / Build on Linux (coverage)
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.
analyze / Build on Linux (coverage)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
analyze / Build on Linux (python_lib)
The following actions use a deprecated Node.js version and will be forced to run on node20: pyTooling/Actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
analyze / Build on Linux (python_lib)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
analyze / Build on Linux (python_lib)
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.
analyze / Build on Linux (fake, gcc_release, clang, simulated)
The following actions use a deprecated Node.js version and will be forced to run on node20: pyTooling/Actions/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
analyze / Build on Linux (fake, gcc_release, clang, simulated)
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.
analyze / Build on Linux (fake, gcc_release, clang, simulated)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
analyze / Build on Linux (fake, gcc_release, clang, simulated)
No files were found with the provided path: /tmp/cores/. No artifacts will be uploaded.
analyze / Build on Linux (gcc_debug)
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/
analyze / Build on Linux (gcc_debug)
The Actions runner is running low on disk space (0.1991 GB available).
analyze / Build on Linux (gcc_debug)
The following actions use a deprecated Node.js version and will be forced to run on node20: pyTooling/Actions/[email protected], 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/
analyze / Build on Linux (gcc_debug)
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.
analyze / Build on Linux (gcc_debug)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
analyze / Build on Darwin (clang, python_lib, simulated)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'