Dotnet build fails with "failed with status code: 51" #301

WillGibson · 2024-07-09T06:11:57Z

WillGibson
Jul 9, 2024

First questions:

Where does this error come from? (I have been searching to no avail)
Where can I find a list of what these status codes mean? (I have been searching to no avail)

As I can't figure out where the aerror somes from, I can't raise and issue on the appropriate repository.

Error...

Paketo Buildpack for .NET Publish 0.12.35
  Executing build process
    Running 'dotnet publish /workspace --configuration Release --runtime linux-x64 --self-contained false --output /tmp/dotnet-publish-output714426815 --verbosity=detailed'
      
      Welcome to .NET 8.0!
      ---------------------
      SDK Version: 8.0.302
      
      Telemetry
      ---------
      The .NET tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.
      
      Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry
      
      ----------------
      Installed an ASP.NET Core HTTPS development certificate.
      To trust the certificate, view the instructions: https://aka.ms/dotnet-https-linux
      
      ----------------
      Write your first app: https://aka.ms/dotnet-hello-world
      Find out what's new: https://aka.ms/dotnet-whats-new
      Explore documentation: https://aka.ms/dotnet-docs
      Report issues and find source on GitHub: https://github.com/dotnet/core
      Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli
      --------------------------------------------------------------------------------------

...usually it hangs there, sometimes it continues with...

      (BuilderBase.h:550 block_for_offset)
       Failed after 1.369560751s
failed to execute 'dotnet publish': signal: trace/breakpoint trap
Timer: Builder ran for 28.694987263s and ended at 2024-07-09T05:50:22Z
ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 51

To replicate, try building the attached DemoDotnet.zip with pack 0.34.2 and the following command...

DOTNET_CLI_TELEMETRY_OPTOUT=1 DOCKER_BUILDKIT=0 pack build platform-demo/dotnet --builder paketobuildpacks/builder-jammy-full --verbose --env BP_DOTNET_PUBLISH_FLAGS="--verbosity=detailed"

I am running it on Apple M1 Pro chip and macOS 14.5.

WillGibson · 2024-07-10T13:02:42Z

WillGibson
Jul 10, 2024
Author

@acodeninja managed to get a more detailed error with…

pack build platform-demo/dotnet --builder paketobuildpacks/builder-jammy-full --verbose --env BP_DOTNET_PUBLISH_FLAGS="--verbosity=detailed" --env BP_DEBUG_ENABLED="true" --env BP_LOG_LEVEL="debug"

      Fatal error. System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
         at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1[[System.Int32, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].GetStateMachineBox[[System.IO.Strategies.BufferedFileStreamStrategy+<ReadAsyncSlowPath>d__37, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](<ReadAsyncSlowPath>d__37 ByRef, StateMachineBox<Int32> ByRef)
         at System.IO.Strategies.BufferedFileStreamStrategy+<ReadAsyncSlowPath>d__37.MoveNext()
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[System.IO.Strategies.BufferedFileStreamStrategy+<ReadAsyncSlowPath>d__37, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](<ReadAsyncSlowPath>d__37 ByRef)
         at System.IO.Strategies.BufferedFileStreamStrategy.ReadAsyncSlowPath(System.Threading.Tasks.Task, System.Memory`1<Byte>, System.Threading.CancellationToken)
         at System.IO.Strategies.BufferedFileStreamStrategy.ReadAsync(System.Memory`1<Byte>, System.Threading.CancellationToken)
         at System.IO.FileStream.ReadAsync(System.Memory`1<Byte>, System.Threading.CancellationToken)
         at System.IO.StreamReader+<ReadBufferAsync>d__72.MoveNext()
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[System.IO.StreamReader+<ReadBufferAsync>d__72, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](<ReadBufferAsync>d__72 ByRef)
         at System.IO.StreamReader.ReadBufferAsync(System.Threading.CancellationToken)
         at System.IO.StreamReader+<ReadLineAsyncInternal>d__63.MoveNext()
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[System.IO.StreamReader+<ReadLineAsyncInternal>d__63, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](<ReadLineAsyncInternal>d__63 ByRef)
         at System.IO.StreamReader.ReadLineAsyncInternal(System.Threading.CancellationToken)
         at System.IO.StreamReader.ReadLineAsync(System.Threading.CancellationToken)
         at System.IO.StreamReader.ReadLineAsync()
         at Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageTransmission+<ReadAddressAsync>d__12.MoveNext()
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageTransmission+<ReadAddressAsync>d__12, dotnet, Version=8.0.302.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ReadAddressAsync>d__12 ByRef)
         at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageTransmission+<ReadAddressAsync>d__12, dotnet, Version=8.0.302.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<ReadAddressAsync>d__12 ByRef)
         at Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageTransmission.ReadAddressAsync(System.IO.TextReader)
         at Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageTransmission+<CreateFromStreamAsync>d__9.MoveNext()
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageTransmission+<CreateFromStreamAsync>d__9, dotnet, Version=8.0.302.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<CreateFromStreamAsync>d__9 ByRef)
         at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageTransmission+<CreateFromStreamAsync>d__9, dotnet, Version=8.0.302.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<CreateFromStreamAsync>d__9 ByRef)
         at Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageTransmission.CreateFromStreamAsync(System.IO.Stream, System.String)
         at Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageService+<LoadTransmissionFromFileAsync>d__20.MoveNext()
         at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageService+<LoadTransmissionFromFileAsync>d__20, dotnet, Version=8.0.302.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<LoadTransmissionFromFileAsync>d__20 ByRef)
         at System.Runtime.CompilerServices.AsyncTaskMethodBuilder`1[[System.__Canon, System.Private.CoreLib, Version=8.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageService+<LoadTransmissionFromFileAsync>d__20, dotnet, Version=8.0.302.0, Culture=neutral, PublicKeyToken=adb9793829ddae60]](<LoadTransmissionFromFileAsync>d__20 ByRef)
         at Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageService.LoadTransmissionFromFileAsync(System.String)
         at Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.StorageService.Peek()
         at Microsoft.DotNet.Cli.Telemetry.PersistenceChannel.Sender.SendLoop()
         at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
         at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef, System.Threading.Thread)
      Failed after 19.806826009s
failed to execute 'dotnet publish': signal: aborted (core dumped)
Timer: Builder ran for 1m29.787249335s and ended at 2024-07-10T11:54:41Z
ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 51

0 replies

sophiewigmore · 2024-07-10T15:35:52Z

sophiewigmore
Jul 10, 2024
Collaborator

Hey there. We don't yet support ARM64/multi-architecture builds, so that might be part of the problem. ☹️ Since you're running on an Apple M1 Pro chip, you might need to build your own M1 images from our official buildpacks for now. It's not ideal, and we have ARM64 in our near future, but if you'd like to try it out check out the instructions a maintainer of our community put together - https://github.com/dmikusa/paketo-arm64

2 replies

sophiewigmore Jul 10, 2024
Collaborator

It might be slow, but if the problem persists, please file an issue over at https://github.com/paketo-buildpacks/dotnet-publish/ and we can investigate the buildpack issue. In the meantime, docs at https://paketo.io/docs/howto/dotnet-core/ might help

WillGibson Jul 10, 2024
Author

I was trying to build it locally for sanity before I try to get it happening in our pipelines.

I think I'll just move direct to trying in the pipeline, which will be a non ARM64 architecture in AWS CodeBuild.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Paketo Buildpacks

Dotnet build fails with "failed with status code: 51" #301

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Paketo Buildpacks

Dotnet build fails with "failed with status code: 51" #301

Uh oh!

WillGibson Jul 9, 2024

Replies: 2 comments · 2 replies

Uh oh!

Uh oh!

WillGibson Jul 10, 2024 Author

Uh oh!

sophiewigmore Jul 10, 2024 Collaborator

Uh oh!

sophiewigmore Jul 10, 2024 Collaborator

Uh oh!

WillGibson Jul 10, 2024 Author

WillGibson
Jul 9, 2024

Replies: 2 comments 2 replies

WillGibson
Jul 10, 2024
Author

sophiewigmore
Jul 10, 2024
Collaborator

sophiewigmore Jul 10, 2024
Collaborator

WillGibson Jul 10, 2024
Author