Skip to content

Add feedback-guided scheduling algorithms #2495

Add feedback-guided scheduling algorithms

Add feedback-guided scheduling algorithms #2495

Triggered via pull request October 14, 2024 18:16
Status Success
Total duration 7m 25s
Artifacts

windowsci.yml

on: pull_request
Build-And-Test-Windows
7m 10s
Build-And-Test-Windows
Fit to window
Zoom out
Zoom in

Annotations

22 warnings
Build-And-Test-Windows
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build-And-Test-Windows
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-dotnet@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/FeedbackGuidedStrategy.cs#L33
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/IScheduleGenerator.cs#L14
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/PCTScheduleGenerator.cs#L48
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/PCTScheduleGenerator.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/PCTScheduleGenerator.cs#L16
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/POSScheduleGenerator.cs#L49
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/POSScheduleGenerator.cs#L17
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/POSScheduleGenerator.cs#L17
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/RandomInputGenerator.cs#L24
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
Build-And-Test-Windows: Src/PChecker/CheckerCore/SystematicTesting/Strategies/Feedback/Generator/RandomInputGenerator.cs#L24
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.
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 '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 'a' 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 'a' 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 'x' only contains lower-cased ascii characters. Such names may become reserved for the language.