Skip to content
build-check

Add atomic fallback for CXX without std::atomic #185

Sign in to view logs

Add atomic fallback for CXX without std::atomic

Add atomic fallback for CXX without std::atomic #185

Triggered via pull request January 17, 2024 10:26
@PetervdPerk-NXPPetervdPerk-NXP
synchronize #319
NXPHoverGames:pr-zenoh-cxx-atomic
Status Failure
Total duration 43s
Artifacts –

build-check.yaml

on: pull_request
Run unit tests on ubuntu-latest
9s
Run unit tests on ubuntu-latest
Check codebase format with clang-format
6s
Check codebase format with clang-format
Build and test in single thread on ubuntu-latest
13s
Build and test in single thread on ubuntu-latest
Test multicast and unicast fragmentation
9s
Test multicast and unicast fragmentation
Matrix: Modular build on ubuntu-latest
Matrix: Build and test raweth transport on ubuntu-latest
Fit to window
Zoom out
Zoom in

Annotations

37 errors
Check codebase format with clang-format
Process completed with exit code 123.
Test multicast and unicast fragmentation
Process completed with exit code 1.
Modular build on ubuntu-latest (0, 0, 1, 0)
Process completed with exit code 2.
Modular build on ubuntu-latest (1, 0, 1, 0)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (1, 0, 1, 0)
Process completed with exit code 2.
Modular build on ubuntu-latest (0, 1, 1, 1)
Process completed with exit code 2.
Modular build on ubuntu-latest (1, 0, 0, 1)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (1, 0, 0, 1)
Process completed with exit code 2.
Build and test raweth transport on ubuntu-latest (0)
Process completed with exit code 2.
Build and test raweth transport on ubuntu-latest (1)
The job was canceled because "_0" failed.
Build and test raweth transport on ubuntu-latest (1)
Process completed with exit code 2.
Run unit tests on ubuntu-latest
Process completed with exit code 2.
Modular build on ubuntu-latest (1, 1, 0, 0)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (1, 1, 0, 0)
Process completed with exit code 2.
Modular build on ubuntu-latest (0, 1, 1, 0)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (0, 1, 1, 0)
Process completed with exit code 2.
Modular build on ubuntu-latest (0, 0, 0, 0)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (0, 0, 0, 0)
Process completed with exit code 2.
Modular build on ubuntu-latest (1, 0, 0, 0)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (1, 0, 0, 0)
Process completed with exit code 2.
Modular build on ubuntu-latest (0, 0, 1, 1)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (0, 0, 1, 1)
The operation was canceled.
Modular build on ubuntu-latest (1, 0, 1, 1)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (1, 0, 1, 1)
The operation was canceled.
Modular build on ubuntu-latest (1, 1, 1, 1)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (1, 1, 1, 1)
The operation was canceled.
Modular build on ubuntu-latest (1, 1, 1, 0)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (1, 1, 1, 0)
The operation was canceled.
Build and test in single thread on ubuntu-latest
Process completed with exit code 2.
Modular build on ubuntu-latest (0, 1, 0, 0)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (0, 1, 0, 0)
The operation was canceled.
Modular build on ubuntu-latest (0, 1, 0, 1)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (0, 1, 0, 1)
The operation was canceled.
Modular build on ubuntu-latest (0, 0, 0, 1)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (0, 0, 0, 1)
The operation was canceled.
Modular build on ubuntu-latest (1, 1, 0, 1)
The job was canceled because "_0_0_1_0" failed.
Modular build on ubuntu-latest (1, 1, 0, 1)
The operation was canceled.