Open anurmatov opened 2 months ago
worth mentioning if you create a container from last succeeded layer (that dotnet restore
step) and run same test/build command it works just fine
I've seen that before but it seemed random.
dotnet build -m:1 --disable-build-servers
thanks for the comment, it's deterministic yes, let me try to test w/ turned off parallelism
still same issue w/ dotnet build -m:1 --disable-build-servers
project structure:
our attempts with different metalama versions (2024.0.16
, 2024.1.23
, 2024.2.19
) aren't working out
tests are passed when running in a container from last succeeded docker layer:
@gfraiteur if needed we can come up with a demo for repro
Hello @anurmatov . May I ask you to collect logs of the failing build? Collecting Metalama logs is described at https://doc.postsharp.net/metalama/conceptual/configuration/creating-logs .
Before we figure this out, a workaround may be to build an empty project with Metalama installed before building the rest of your projects. The version of Metalama in the project must match the version used in your project.
hello @prochan2, attached logs to the ticket, please find them here support.postsharp.net
trying to get a workaround to work - no luck yet
@anurmatov This was fixed in 2024.2.21, the configuration
(any casing) env var should be now removed for the helper project build.
Environment
Metalama.Framework Version: 2024.2.19 Runtime: .NET 8.0.1 OS: Debian GNU/Linux 12 (bookworm) Docker Base Image: mcr.microsoft.com/dotnet/sdk:8.0-bookworm-slim
Issue Description
During our Docker build process, Metalama is encountering a DirectoryNotFoundException. The build (same with
dotnet test
) fails when trying to access a directory that doesn't exist.Error message
Stack Trace
from metalama crash log file:
Dockerfile
Additonal context