-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: PublishCodeCoverageResults@2 failing with Syntax error: word unexpected (expecting ")") on ARM64 #19346
Comments
PublishCodeCoverageResults@2 is also failing on our AWS ARM64 ec2 self hosted instance. Error reported by task:
|
Similar problem as @tscott-au on our self hosted AWS EC2 ARM64 instance running Ubuntu 22.04.
In our case, we're performing some cross compilation tasks so we've set up qemu with binfmt. Looks like when
IMO the solution would be shipping |
New issue checklist
Task name
PublishCodeCoverageResults
Task version
2
Issue Description
The task stopped working after changing the agent to run on Ubuntu 22.04 ARM64 instead of the previous AmazonLinux2 x64. Looking at the path of the used tool (with
linux-x64
in it) it seems like the task is not compiled to run on ARM64 machines.Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 22.04 ARM64
Relevant log output
/anonymized/_tasks/PublishCodeCoverageResults_2a7ebc54-c13e-490e-81a5-d7561ab7cd97/2.229.0/node_modules/coveragepublisher/CoveragePublisher/linux-x64/CoveragePublisher.Console /anonymized/cobertura-coverage.xml --reportDirectory /anonymized --sourceDirectory /anonymized/_tasks/PublishCodeCoverageResults_2a7ebc54-c13e-490e-81a5-d7561ab7cd97/2.229.0/node_modules/coveragepublisher/CoveragePublisher/linux-x64/CoveragePublisher.Console: 9: Syntax error: word unexpected (expecting ")")
Full task logs with system.debug enabled
Repro steps
No response
The text was updated successfully, but these errors were encountered: