Receiving error trying to update amazon.lambda.tools global tool when running two sam build commands concurrently
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws
- Domain
- build-system
Research direction
Start by reproducing concurrent sam build commands on a Windows build host using two workspaces and a dotnetcore3.1 Lambda. Read the related issues #126 and #127 for the proposed direction; done means concurrent builds no longer fail while updating the Amazon.Lambda.Tools global tool.
Written by the indexing model from the issue text.
Description
Description:
Receiving error from sam build when building a dotnet core 3.1 lambda function on a CI build server that is running more than one agent.
Error: DotnetCliPackageBuilder:GlobalToolInstall - Error configuring the Amazon.Lambda.Tools .NET Core Global Tool: Dotnet CLI Failed: Tool 'amazon.lambda.tools' failed to update due to the following:
Failed to uninstall tool 'amazon.lambda.tools': Failed to retrieve tool configuration: The process cannot access the file 'C:\Users\CruiseControl\.dotnet\tools\.store\amazon.lambda.tools\4.3.0\amazon.lambda.tools\4.3.0\tools\netcoreapp2.1\any\DotnetToolSettings.xml' because it is being used by another process.
Steps to reproduce the issue:
- Create a SAM project that includes a lambda with the dotnetcore3.1 runtime
- Create two different workspaces with the same code on your machine
- run
sam buildconcurrently until the file locking issue is encountered
Additional environment details (Ex: Windows, Mac, Amazon Linux etc) observed on a windows build host
This seems related to #126 and would likely be resolved by #127 as well. Is there any timeline for releasing that change?
- Dominant language
- Python
- Stars
- 381
- Forks
- 162
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 2
Contributor 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 aws/aws-lambda-builders
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
aws/aws-lambda-builders#925 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 64/100
aws/aws-lambda-builders#924 · 1 comment ·
-
Bug: PythonUvBuilder fails to build app with dependencies on editable installs in the workspace Openstage/needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 25/100
aws/aws-lambda-builders#892 ·
-
stage/needs-triage type/feature
Difficulty 4/5 3-5 days Newbie friendliness 38/100
aws/aws-lambda-builders#839 · 2 comments · 1 reaction ·
-
area/build contributors/good-first-issue contributors/welcome type/feature
Difficulty 4/5 3-5 days Newbie friendliness 38/100
aws/aws-lambda-builders#831 · 3 comments ·
All issues in aws/aws-lambda-builders
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·