Skip to content

fix(plc4go/bacnet): tag related issues #962

fix(plc4go/bacnet): tag related issues

fix(plc4go/bacnet): tag related issues #962

Triggered via push August 20, 2024 08:47
Status Failure
Total duration 1h 49m 48s
Artifacts 3

go-platform.yml

on: push
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 25 warnings
test (17, macos-latest)
Resource not accessible by integration
test (17, windows-latest)
Resource not accessible by integration
test (17, ubuntu-latest)
Resource not accessible by integration
test (17, macos-latest)
Resource not accessible by integration
test (17, macos-latest)
Resource not accessible by integration
test (17, macos-latest)
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
test (17, macos-latest)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.18.2.
test (17, macos-latest)
Failed to check available disk space: Error: Command failed: df -Pk -- /Users/runner/work/plc4x/plc4x dyld[4855]: terminating because inserted dylib '/Users/runner/hostedtoolcache/CodeQL/2.18.2/arm64/codeql/tools/osx64/libtrace.dylib' could not be loaded: tried: '/Users/runner/hostedtoolcache/CodeQL/2.18.2/arm64/codeql/tools/osx64/libtrace.dylib' (fat file, but missing compatible architecture (have 'x86_64,arm64', need 'arm64e')), '/System/Volumes/Preboot/Cryptexes/OS/Users/runner/hostedtoolcache/CodeQL/2.18.2/arm64/codeql/tools/osx64/libtrace.dylib' (no such file), '/Users/runner/hostedtoolcache/CodeQL/2.18.2/arm64/codeql/tools/osx64/libtrace.dylib' (fat file, but missing compatible architecture (have 'x86_64,arm64', need 'arm64e')) dyld[4855]: tried: '/Users/runner/hostedtoolcache/CodeQL/2.18.2/arm64/codeql/tools/osx64/libtrace.dylib' (fat file, but missing compatible architecture (have 'x86_64,arm64', need 'arm64e')), '/System/Volumes/Preboot/Cryptexes/OS/Users/runner/hostedtoolcache/CodeQL/2.18.2/arm64/codeql/tools/osx64/libtrace.dylib' (no such file), '/Users/runner/hostedtoolcache/CodeQL/2.18.2/arm64/codeql/tools/osx64/libtrace.dylib' (fat file, but missing compatible architecture (have 'x86_64,arm64', need 'arm64e'))
test (17, macos-latest)
Resource not accessible by integration
test (17, macos-latest)
Resource not accessible by integration
test (17, macos-latest)
Resource not accessible by integration
test (17, macos-latest)
Resource not accessible by integration
test (17, windows-latest)
Resource not accessible by integration
test (17, windows-latest)
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
test (17, windows-latest)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.18.2.
test (17, windows-latest)
Resource not accessible by integration
test (17, windows-latest)
Resource not accessible by integration
test (17, windows-latest)
Resource not accessible by integration
test (17, windows-latest)
Resource not accessible by integration
test (17, windows-latest)
Resource not accessible by integration
test (17, ubuntu-latest)
Resource not accessible by integration
test (17, ubuntu-latest)
Resource not accessible by integration
test (17, ubuntu-latest)
Resource not accessible by integration
test (17, ubuntu-latest)
Resource not accessible by integration
test (17, ubuntu-latest)
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
test (17, ubuntu-latest)
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.18.2.
test (17, ubuntu-latest)
Resource not accessible by integration
test (17, ubuntu-latest)
Resource not accessible by integration

Artifacts

Produced during runtime
Name Size
golang-test-report-macos-latest
46 KB
golang-test-report-ubuntu-latest
46.1 KB
golang-test-report-windows-latest
46.3 KB