exrm fails due to unreachable_package - release

First time trying out exrm. Build failing because unreachable_package. Can't seem to find what package is the issue. Any insight into where I should be looking would be much appreciated.
===> Provider successfully run: app_discover
===> Running provider resolve_release
===> Solving Release telnet_client-0.0.1
===> Provider (resolve_release) failed with: {error,
{rlx_prv_release,
{failed_solve,
{unreachable_package,
telnet_client}}}}
==> Failed to build release. Please fix any errors and try again.

Removing the build_path and config_path seems to have done the trick.
build_path: "../../_build",
config_path: "../../config/config.exs",

Related

Azure Devops Pipeline build fails hudson.security.AccessDeniedException3: *** is missing the Job/Build permission

I am using Jenkins to run build which is integrated to Azure Devops.
My Azure Pipeline build fails with the error:
Job creation failed.
HttpResponse.statusCode=500
HttpResponse.statusMessage=Server Error
hudson.security.AccessDeniedException3: *** is missing the Job/Build permission
Where can I start looking to troubleshoot this error, please?
Regards and Thanks for the help
This has been resolved. The issue was there was no permission from my jenkins build user. I just gave the build attribute permission to the user from within the Jenkins platform

No test result files matching D:\build\V1\_w\1\s\test\target\reports\*.xml were found

I have configured azure pipeline for running my build.
While running test case step the build ran with status “success” with message: No test result files matching D:\build\V1_w\1\s\test\target\reports*.xml were found, so publishing JUnit test results is being skipped”
And after this when zip file is creating automatically as part of build “create zip with failed tests info” it failed the build with error message: ##[error] Error: Achieve creation failed for archive file: D:\build\V1_w\1\s\tests\target\reports.zip ENOENT
Please help me to resolve this issue.
I have done all the required right configuration but still it’s occurring.
Thanks 🙏

Failed to create snap, snap command failed

I am trying to build a snap and i have used flutter for building the app. while creating the snap package i am getting an error.
Staging flutter-extension
+ snapcraftctl stage
Staging gnome-3-28-extension
+ snapcraftctl stage
Staging system-information
+ snapcraftctl stage
Priming flutter-extension
+ snapcraftctl prime
Priming gnome-3-28-extension
+ snapcraftctl prime
Priming system-information
+ snapcraftctl prime
The command 'system_information' for 'system_information' was resolved to 'bin/system_information'.
The command 'system_information' has been changed to 'bin/system_information'.
Snapping |
Failed to create snap, snap command failed:
stdout:
stderr:
error: cannot pack "/root/prime": mksquashfs call failed: Could not create destination file: Operation not permitted
We would appreciate it if you anonymously reported this issue.
No other data than the traceback and the version of snapcraft in use will be sent.
Would you like to send this error data? (Yes/No/Always/View) [no]: no
snapcraft-system-information #
I have tried snapcraft clean already but it didn't cleared the issue.
Delete build directory and build again.
follow this github link for detail
https://github.com/EOSIO/eos/issues/4885
Actually the error is generating from multipass which i used to build my snap packages. I tried deleting /build and building again but it didn't worked.
I found an alternate way to build snaps using lxd

VSTS - Build a Docker Image

I have a .NET Core repo in VSTS. I'm trying to create a Build pipeline that builds a Docker image and adds it to my Azure Container Registry. My Build pipeline has a Docker task. This task has the "Build an image" action selected. This action relies on my Dockerfile, which looks like this:
FROM microsoft/dotnet:2.1.2-runtime-nanoserver-1803
# Install .NET Core
ENV DOTNET_VERSION 2.1.2
When my Build pipeline runs, I get an error that says:
failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage \\?\C:\ProgramData\docker\windowsfilter\82aba535faccd8bf0e5ce3c122247672fa671214000a12c5481972212c5e2ca0\UtilityVM: The system cannot find the path specified.
##[error]C:\Program Files\Docker\docker.exe failed with return code: 1
Why am I getting this error? How do I fix it?
It should be the same issue with this one : https://github.com/Microsoft/vsts-tasks/issues/6510
Seems it still have some issues with nanoserver-1803
Just try to setup and host a custom agent on Azure VM, then check it again.
https://github.com/Microsoft/vsts-tasks/issues/6510#issuecomment-370152300
I found maybe an explication about this error: VSTS agents seem not
support nanoserver-1709 actually. Maybe this will change with the next
version 1803.
See details here: Microsoft/vsts-agent#1393
When I setup and host a custom agent on a machine on Azure, it's
working. So it's not a bug with this task. I close this issue. Thanks!

Odd Websocket Error at Build Time - "Unable to Resolve websocket/lib/BufferUtil"?

Even though I have Websocket installed, at build time, using the Meteor build tool, I’m getting this console error:
Unable to resolve some modules:
"../build/Release/bufferutil" in /Volumes/RAM Disk/myWebApp/node_modules/websocket/lib/BufferUtil.js (os.osx.x86_64)
"../build/default/bufferutil" in /Volumes/RAM Disk/myWebApp/node_modules/websocket/lib/BufferUtil.js (os.osx.x86_64)
"../build/Release/validation" in /Volumes/RAM Disk/myWebApp/node_modules/websocket/lib/Validation.js (os.osx.x86_64)
"../build/default/validation" in /Volumes/RAM Disk/myWebApp/node_modules/websocket/lib/Validation.js (os.osx.x86_64)
What might be causing this?
It looks like this is just a warning, not a fatal error.
https://github.com/meteor/meteor/issues/6601

Resources