Skip to content

Revert "replace --task with --output" #32

Revert "replace --task with --output"

Revert "replace --task with --output" #32

Triggered via pull request February 7, 2025 07:02
Status Success
Total duration 1m 53s
Artifacts 4

release.yml

on: pull_request
Matrix: build
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
build (ubuntu-24.04): EmpireCompiler/Program.cs#L45
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build (ubuntu-24.04): EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
build (ubuntu-24.04-arm): EmpireCompiler/Program.cs#L45
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build (ubuntu-24.04-arm): EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
build (macos-15)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build (macos-15): EmpireCompiler/Program.cs#L45
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build (macos-15): EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
build (macos-13)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build (macos-13): EmpireCompiler/Program.cs#L45
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build (macos-13): EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.

Artifacts

Produced during runtime
Name Size Digest
EmpireCompiler-linux-arm64 Expired
94 MB
sha256:96f6f93ca90f60190fbb6a1e9ce186bd31a6521f7c6f620131c47edfeeae8409
EmpireCompiler-linux-x64 Expired
95.9 MB
sha256:236eac850c3d33ca6fa5e09ab824e6dc047b0e0846a0a5c555910be1ca4528b3
EmpireCompiler-osx-arm64 Expired
94.8 MB
sha256:59a2944e6413edf4735b0f46d9bda7ac376f6b698b1b6444cac52486d3d104ad
EmpireCompiler-osx-x64 Expired
96.6 MB
sha256:7c0bb029b8045335452d5e3112b6a6b4689eefbe74f52020e446ce19a5884380