Skip to content

CodeQL

CodeQL #346

Triggered via schedule October 4, 2024 05:22
Status Failure
Total duration 6h 1m 56s
Artifacts

codeql.yml

on: schedule
analyze  /  Build on Linux (gcc_debug)
2h 40m
analyze / Build on Linux (gcc_debug)
analyze  /  Build on Linux (fake, gcc_release, clang, simulated)
59m 47s
analyze / Build on Linux (fake, gcc_release, clang, simulated)
analyze  /  Build on Linux (python_lib)
21m 49s
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)
13m 58s
analyze / Build on Linux (coverage)
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 36 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.19.0/x64/codeql/codeql database run-queries --ram=14576 --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 DataFlowPrivate::nodeHasOperand/3#9d22a194/3@i2#600faxvc Severe disk cache trouble (corruption or out of space) at /__w/_temp/codeql_databases/cpp/db-cpp/default/cache/pages/82.pack: Failed to write item to disk The RA to evaluate was: {3} r1 = `DataFlowUtil::hasOperandAndIndex/3#7f99de51#prev_delta` AND NOT `DataFlowPrivate::nodeHasOperand/3#9d22a194#prev`(FIRST 3) 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.RecursiveLayer$RecursiveWork.doWork(RecursiveLayer.java:440) 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/82.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.deliverAndWriteSortedTuples(IntArraySorter.java:290) at com.semmle.inmemory.relations.IntArraySorter.sortAndDeliverCompletePages(IntArraySorter.java:118) at com.semmle.inmemory.relations.writers.IntArrayWriter.sortAndDeliverCompletePages(IntArrayWriter.java:244) 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:83) 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(SimpleStep.java:130) at com.semmle.inmemory.pipeline.ExpanderStep$ExpanderState.deliverMatchOutput(ExpanderStep.java:85) at com.semmle.inmemory.pipel
analyze / Build on Darwin (clang, python_lib, simulated)
The job running on runner GitHub Actions 17 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/with-post-step@v0.4.5. 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/with-post-step@v0.4.5. 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/with-post-step@v0.4.5. 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/with-post-step@v0.4.5. 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)
`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 (fake, gcc_release, clang, simulated)
Resource not accessible by integration
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)
Resource not accessible by integration
analyze / Build on Linux (fake, gcc_release, clang, simulated)
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
analyze / Build on Linux (fake, gcc_release, clang, simulated)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.19.0.
analyze / Build on Linux (fake, gcc_release, clang, simulated)
Resource not accessible by integration
analyze / Build on Linux (gcc_debug)
Resource not accessible by integration
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.2454 GB available).
analyze / Build on Linux (gcc_debug)
Resource not accessible by integration
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/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/
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 Linux (gcc_debug)
Resource not accessible by integration
analyze / Build on Linux (gcc_debug)
Resource not accessible by integration
analyze / Build on Linux (gcc_debug)
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
analyze / Build on Linux (gcc_debug)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.19.0.
analyze / Build on Linux (gcc_debug)
Resource not accessible by integration
analyze / Build on Darwin (clang, python_lib, simulated)
Resource not accessible by integration
analyze / Build on Darwin (clang, python_lib, simulated)
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
analyze / Build on Darwin (clang, python_lib, simulated)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.19.0.
analyze / Build on Darwin (clang, python_lib, simulated)
Resource not accessible by integration
analyze / Build on Darwin (clang, python_lib, simulated)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
analyze / Build on Darwin (clang, python_lib, simulated)
Resource not accessible by integration