CI failure: "Blazor Wasm" `command docker build... returned exit code 1`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, wasm
- Domain
- build-system, ci-cd
Research direction
Start with the linked Azure DevOps build log to find the Docker build error beyond the reported exit code. Inspect src/Components/benchmarkapps/Wasm.Performance/dockerfile and reproduce the command against that directory; done means the Blazor Wasm benchmark job completes successfully in CI.
Written by the indexing model from the issue text.
Description
/cc @sebastienros
==============================================================================
Task : Blazor Wasm
Description : Sends a message to Azure Service Bus using a service connection (no agent is required)
Version : 1.221.0
Author : Microsoft Corporation
Help URL : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/publish-to-azure-service-bus
==============================================================================
[04:01:36.789] Running session '20240523.1' with description ''
[04:01:36.806] Starting job 'application' ...
[04:01:36.807] Submitted job: http://asp-perf-lin:5001/jobs/203
[04:01:37.816] 'application' has been selected by the server ...
[04:01:37.816] 'application' is now building ... http://asp-perf-lin:5001/jobs/203/buildlog
[04:05:59.971] 'application' failed on agent, stopping...
An unexpected error occurred while building the job: One or more errors occurred. (Command docker build --pull --build-arg gitBranch=main -t benchmarks_dockerfile -f src/Components/benchmarkapps/Wasm.Performance/dockerfile /tmp/benchmarks-agent/benchmarks-server-1/4jjb4rom.sqp/src/Components/benchmarkapps/Wasm.Performance returned exit code 1)
[04:05:59.973] Stopping job 'application' ...
An unexpected error occurred while building the job: One or more errors occurred. (Command docker build --pull --build-arg gitBranch=main -t benchmarks_dockerfile -f src/Components/benchmarkapps/Wasm.Performance/dockerfile /tmp/benchmarks-agent/benchmarks-server-1/4jjb4rom.sqp/src/Components/benchmarkapps/Wasm.Performance returned exit code 1)
[04:06:00.978] Deleting job 'application' ...
| application | | |
| ----------- | - | - |
- Dominant language
- C#
- Stars
- 1.2k
- Forks
- 244
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aspnet/Benchmarks
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
aspnet/Benchmarks#2226 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aspnet/Benchmarks#2015 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/Benchmarks#2204 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aspnet/Benchmarks#2161 ·
-
Test io_uring impactOpen
Difficulty 4/5 3-5 days Newbie friendliness 20/100
aspnet/Benchmarks#2153 · 21 reactions ·
All issues in aspnet/Benchmarks
Similar issues
-
area-NavigationView bug needs-triage team-Controls
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/microsoft-ui-xaml#12671 · 3 comments ·
Maintainers usually reply within 2 days
-
Retarget the extension to Fallout 10.5Possibly taken @ChrisonSimtian claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Improve time codes: status hint doesn't mention the new Shift+F7 / Shift+F8 "to check" navigationOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
SubtitleEdit/subtitleedit#16943 ·
Maintainers usually reply within 1 day