Skip to content
RTPProxy CI

RTPProxy CI #806

Sign in to view logs

RTPProxy CI

RTPProxy CI #806

Triggered via schedule March 2, 2025 01:52
@sobomaxsobomax
⁠ faa198b
master
Status Success
Total duration 2h 1m 12s
Artifacts –
This run and associated checks have been archived and are scheduled for deletion. Learn more about checks retention

rtpproxy_ci.yml

on: schedule
Load Jobs Settings  /  Disabled Actions
2s
Load Jobs Settings / Disabled Actions
Matrix: Lean Build
Matrix: Full Build
Matrix: Functional Testing
Matrix: Glitch Injection
Matrix: Fuzz with OSS-Fuzz
Matrix: Build&Push to DockerHub
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 24 warnings
Fuzz with OSS-Fuzz (undefined)
CodeQL Action major versions v1 and v2 have been deprecated. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2025-01-10-code-scanning-codeql-action-v2-is-now-deprecated/
Fuzz with OSS-Fuzz (memory)
CodeQL Action major versions v1 and v2 have been deprecated. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2025-01-10-code-scanning-codeql-action-v2-is-now-deprecated/
Fuzz with OSS-Fuzz (address)
CodeQL Action major versions v1 and v2 have been deprecated. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2025-01-10-code-scanning-codeql-action-v2-is-now-deprecated/
Lean Build (20.04, gcc-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Lean Build (20.04, clang-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Lean Build (20.04, gcc-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Lean Build (20.04, gcc)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Lean Build (20.04, clang)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Lean Build (20.04, clang-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Full Build (20.04, gcc-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Full Build (20.04, clang)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Full Build (20.04, gcc-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Full Build (20.04, clang-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Full Build (20.04, gcc)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Full Build (20.04, clang-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Functional Testing (20.04, gcc-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Functional Testing (20.04, gcc-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Functional Testing (20.04, gcc)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Functional Testing (20.04, clang-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Functional Testing (20.04, clang)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Functional Testing (20.04, clang-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Glitch Injection (20.04, clang-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Glitch Injection (20.04, clang-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Glitch Injection (20.04, gcc)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Glitch Injection (20.04, gcc-10)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Glitch Injection (20.04, clang)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101
Glitch Injection (20.04, gcc-9)
The Ubuntu-20.04 brownout takes place from 2025-02-01. For more details, see https://github.com/actions/runner-images/issues/11101