Skip to content

Clarify usage of history variables in error messages #6493

Clarify usage of history variables in error messages

Clarify usage of history variables in error messages #6493

Workflow file for this run

name: "CodeQL"
on:
push:
branches: [ develop ]
pull_request:
branches: [ develop ]
jobs:
# This job takes approximately 82 minutes
analyze:
name: Analyze
runs-on: ubuntu-latest
permissions:
actions: read
contents: read
security-events: write
strategy:
fail-fast: false
matrix:
language: [ 'cpp', 'java', 'javascript', 'python' ]
steps:
- name: Checkout repository
uses: actions/checkout@v4
with:
submodules: recursive
# Initializes the CodeQL tools for scanning.
- name: Initialize CodeQL
uses: github/codeql-action/init@v3
with:
languages: ${{ matrix.language }}
# If you wish to specify custom queries, you can do so here or in a config file.
# By default, queries listed here will override any specified in a config file.
# Prefix the list here with "+" to use these queries and those in the config file.
# queries: ./path/to/local/query, your-org/your-repo/queries@main
- name: Install dependencies
run: |
sudo apt-get update
sudo apt-get install --no-install-recommends -yq maven flex bison
- name: Build
run: |
make -C src minisat2-download
make -C src -j4
make -C unit -j4
make -C jbmc/src -j4
make -C jbmc/unit -j4
- name: Perform CodeQL Analysis
uses: github/codeql-action/analyze@v3