Skip to content

Use @nested annotation as a standards compliant way to annotate whether we have a top level type or not #1030

Use @nested annotation as a standards compliant way to annotate whether we have a top level type or not

Use @nested annotation as a standards compliant way to annotate whether we have a top level type or not #1030

Triggered via pull request February 15, 2024 11:30
Status Cancelled
Total duration 1h 28m 9s
Artifacts

linux.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

13 errors
ubuntu-20.04 g++-7 ruby-2.5
Process completed with exit code 1.
ubuntu-20.04 g++-8 ruby-2.6
Process completed with exit code 1.
ubuntu-20.04 g++-10 ruby-3.0
Process completed with exit code 1.
ubuntu-22.04 g++-11 ruby-3.1
Canceling since a higher priority waiting request for 'linux-refs/pull/428/merge' exists
ubuntu-22.04 g++-11 ruby-3.1
The operation was canceled.
ubuntu-20.04 g++-9 ruby-2.7
Canceling since a higher priority waiting request for 'linux-refs/pull/428/merge' exists
ubuntu-20.04 g++-9 ruby-2.7
The operation was canceled.
ubuntu-22.04 g++-11 ruby-3.0
Canceling since a higher priority waiting request for 'linux-refs/pull/428/merge' exists
ubuntu-22.04 g++-11 ruby-3.0
The operation was canceled.
ubuntu-22.04 g++-12 ruby-3.1
Canceling since a higher priority waiting request for 'linux-refs/pull/428/merge' exists
ubuntu-22.04 g++-12 ruby-3.1
The operation was canceled.
ubuntu-22.04 g++-13 ruby-3.1
Canceling since a higher priority waiting request for 'linux-refs/pull/428/merge' exists
ubuntu-22.04 g++-13 ruby-3.1
The operation was canceled.