Skip to content

[PVerifier] exception handling for PVerifier-specific tokens (#906) #3037

[PVerifier] exception handling for PVerifier-specific tokens (#906)

[PVerifier] exception handling for PVerifier-specific tokens (#906) #3037

Triggered via push August 15, 2025 03:32
Status Success
Total duration 12m 24s
Artifacts

windowsci.yml

on: push
Build-And-Test-Windows
12m 20s
Build-And-Test-Windows
Fit to window
Zoom out
Zoom in

Annotations

14 warnings and 1 notice
Build-And-Test-Windows
The type name 'ev' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'ev' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'y' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'a' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'x' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'y' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'a' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'x' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'x' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows
The type name 'x' only contains lower-cased ascii characters. Such names may become reserved for the language.
Build-And-Test-Windows: Tst/UnitTests/TypeCheckingUtilsTest.cs#L3
The using directive for 'NUnit.Framework' appeared previously in this namespace
Build-And-Test-Windows: Tst/UnitTests/TypeCheckingUtilsTest.cs#L3
The using directive for 'NUnit.Framework' appeared previously in this namespace
Build-And-Test-Windows
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677