remove Sonar

Author: pavel-kirienko

.github/workflows/main.yml

@@ -1,7 +1,7 @@
 name: Main Workflow
 on: [push, pull_request]
 env:
-  LLVM_VERSION: 15
+  LLVM_VERSION: 19
 jobs:
   test:
     if: github.event_name == 'push'
@@ -39,78 +39,12 @@ jobs:
       - working-directory: ${{github.workspace}}/build
         run: make test
 
-  sonarcloud:
-    if: >
-      github.event_name == 'pull_request'                   ||
-      contains(github.ref, '/master')                       ||
-      contains(github.ref, '/release')                      ||
-      contains(github.event.head_commit.message, '#sonar')
-    runs-on: ubuntu-latest
-    env:
-      SONAR_SCANNER_VERSION: 5.0.1.3006
-      SONAR_SERVER_URL: "https://sonarcloud.io"
-      BUILD_WRAPPER_OUT_DIR: build_wrapper_output_directory
-      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
-      CC: gcc
-      CXX: g++
-    steps:
-    - uses: actions/checkout@v4
-      with:
-        fetch-depth: 0
-    - run: sudo apt install g++ g++-multilib gcc-multilib
-    - uses: actions/setup-java@v4
-      with:
-        java-version: 17
-        distribution: zulu
-    - uses: actions/cache@v4
-      with:
-        path: ~/.sonar/cache
-        key: ${{ runner.os }}-sonar
-        restore-keys: ${{ runner.os }}-sonar
-    - name: Download and set up sonar-scanner
-      env:
-        SONAR_SCANNER_DOWNLOAD_URL: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-${{ env.SONAR_SCANNER_VERSION }}-linux.zip
-      run: |
-        mkdir -p $HOME/.sonar
-        curl -sSLo $HOME/.sonar/sonar-scanner.zip ${{ env.SONAR_SCANNER_DOWNLOAD_URL }}
-        unzip -o $HOME/.sonar/sonar-scanner.zip -d $HOME/.sonar/
-        echo "$HOME/.sonar/sonar-scanner-${{ env.SONAR_SCANNER_VERSION }}-linux/bin" >> $GITHUB_PATH
-    - name: Download and set up build-wrapper
-      env:
-        BUILD_WRAPPER_DOWNLOAD_URL: ${{ env.SONAR_SERVER_URL }}/static/cpp/build-wrapper-linux-x86.zip
-      run: |
-        curl -sSLo $HOME/.sonar/build-wrapper-linux-x86.zip ${{ env.BUILD_WRAPPER_DOWNLOAD_URL }}
-        unzip -o $HOME/.sonar/build-wrapper-linux-x86.zip -d $HOME/.sonar/
-        echo "$HOME/.sonar/build-wrapper-linux-x86" >> $GITHUB_PATH
-    # Pass NDEBUG to exclude assert() from coverage; see https://github.com/pavel-kirienko/o1heap/issues/9
-    - name: Run build-wrapper
-      run: |
-        cmake tests -DCMAKE_BUILD_TYPE=Debug -DNO_STATIC_ANALYSIS=1 -DCMAKE_C_FLAGS='-DNDEBUG=1'
-        build-wrapper-linux-x86-64 --out-dir ${{ env.BUILD_WRAPPER_OUT_DIR }} make all
-        make test
-        gcov --preserve-paths --long-file-names $(find CMakeFiles/test_general_cov.dir -name '*.gcno')
-        gcov --preserve-paths --long-file-names $(find CMakeFiles/test_private_cov.dir -name '*.gcno')
-    # https://community.sonarsource.com/t/analyzing-a-header-only-c-library/51468
-    - if: env.SONAR_TOKEN != ''
-      run: >
-        sonar-scanner
-        --define sonar.projectKey="pavel-kirienko_o1heap"
-        --define sonar.organization="pavel-kirienko"
-        --define sonar.sources="o1heap/"
-        --define sonar.sourceEncoding="UTF-8"
-        --define sonar.cfamily.gcov.reportsPath="."
-        --define sonar.cfamily.build-wrapper-output="${{ env.BUILD_WRAPPER_OUT_DIR }}"
-        --define sonar.host.url="${{ env.SONAR_SERVER_URL }}"
-        --define sonar.login=${{ secrets.SONAR_TOKEN }}
-        $([ -z "$GITHUB_BASE_REF" ] && echo "--define sonar.branch.name=${GITHUB_REF##*/}" || true)
-
   style_check:
     if: github.event_name == 'push'
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - uses: DoozyX/clang-format-lint-action@v0.15
+      - uses: DoozyX/clang-format-lint-action@v0.20
         with:
           source: './o1heap ./tests'
           exclude: './tests/catch'

README.md

@@ -1,10 +1,8 @@
 # O(1) heap
 
 [![Main Workflow](https://github.com/pavel-kirienko/o1heap/actions/workflows/main.yml/badge.svg)](https://github.com/pavel-kirienko/o1heap/actions/workflows/main.yml)
-[![Reliability Rating](https://sonarcloud.io/api/project_badges/measure?project=pavel-kirienko_o1heap&metric=reliability_rating)](https://sonarcloud.io/dashboard?id=pavel-kirienko_o1heap)
-[![Coverage](https://sonarcloud.io/api/project_badges/measure?project=pavel-kirienko_o1heap&metric=coverage)](https://sonarcloud.io/dashboard?id=pavel-kirienko_o1heap)
 
-O1heap is a highly deterministic constant-complexity memory allocator designed for
+O1Heap is a highly deterministic constant-complexity memory allocator designed for
 hard real-time high-integrity embedded systems.
 The name stands for *O(1) heap*.
 
@@ -254,15 +252,6 @@ The following tools should be available locally to conduct library development:
 - An AMD64 machine.
 - (optional) Valgrind.
 
-### Conventions
-
-The codebase shall follow the [Zubax C/C++ Coding Conventions](https://kb.zubax.com/x/84Ah).
-Compliance is enforced through the following means:
-
-- Clang-Tidy -- invoked automatically while building the test suite.
-- Clang-Format -- invoked manually as `make format`; enforced in CI/CD automatically.
-- SonarCloud -- invoked by CI/CD automatically.
-
 ### Testing
 
 Please refer to the continuous integration configuration to see how to invoke the tests.
@@ -273,32 +262,26 @@ Update the version number macro in the header file and create a new git tag like
 
 ### MISRA compliance
 
-MISRA compliance is enforced with the help of the following tools:
+MISRA compliance is enforced with the help of:
 
 - Clang-Tidy -- invoked automatically during the normal build process.
-- SonarCloud -- invoked as part of the continuous integration build.
 
 Every intentional deviation shall be documented and justified in-place using the following notation,
 followed by the appropriate static analyser warning suppression statement:
 
 ```c
 // Intentional violation of MISRA: <valid reason here>
-// NOSONAR
-// NOLINT
+// NOLINT(*-specific-rule)
 ```
 
 The list of intentional deviations can be obtained by simply searching the codebase for the above comments.
 
-Do not suppress compliance warnings using the means provided by static analysis tools because such deviations
-are impossible to track at the source code level.
-An exception applies for the case of false-positive (invalid) warnings -- those should not be mentioned in the codebase.
-
 ## Further reading
 
 - [Timing-Predictable Memory Allocation In Hard Real-Time Systems](https://publikationen.sulb.uni-saarland.de/bitstream/20.500.11880/26614/1/diss.pdf), J. Herter, 2014.
 - [Worst case fragmentation of first fit and best fit storage allocation strategies](https://academic.oup.com/comjnl/article/20/3/242/751782), J. M. Robson, 1975.
 - [Dynamic Memory Allocation In SQLite](https://sqlite.org/malloc.html) -- on Robson proof and deterministic fragmentation.
-- *[Russian]* [Динамическая память в системах жёсткого реального времени](https://habr.com/ru/post/486650/) -- issues with dynamic memory allocation in modern embedded RTOS and related popular misconceptions.
+- [Динамическая память в системах жёсткого реального времени](https://habr.com/ru/post/486650/) -- issues with dynamic memory allocation in modern embedded RTOS and related popular misconceptions.
 
 ## Changelog