-
Notifications
You must be signed in to change notification settings - Fork 870
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]: v4.248.0 Unable to perform source delete of build directory #5104
Comments
I'm seeing a similar issue on some builds on some newly set up self-hosted agents, also running 4.248.0, but on Ubuntu 24.04.
|
Example error with debug enabled.
|
Also confirming that the same issue does not occur when using a v3 agent (v3.248.1). |
We are having exact same libperl issue
Agent used - v4.251.0 on Ubuntu 22.04 libperl.so is a symlink to libperl.so.5.38.0 which is not available
Those libperl files were installed here by one of the previous jobs which build Yocto related stuff. I am not sure if azure client tried to remove all content of _work/112 dir and definitelly I do not understand why it try to access libperl.so file. Any idea how it could be debug further? I think the only workaround would be to remove whole $Pipeline.Workspace after every job but I think that this is the same what |
And I think that I can also confirm that it was working on v3.x.x (in our case v3.248.0) |
What happened?
Error occurs in Initialize Job when attempting to delete a file in the s directory. We did not have any issues with v3.251.0.
After running into the issue, we reverted back to v3.251.0 and the error went away. This occurred on Linux 22-04 x86/64 and ARM64 systems.
Logs attached (some names were changed for the sake of public sharing, but all of the information is as it occurred in the logs).
Bullseye is referenced as it includes both the ARM and AMD CPU types. It failed on all distributions we compiled for (Ubuntu and Debian)
Setup:
Base Linux 22.04 Build agent
Bullseye container for both x86/64 and ARM64
Build process Debian make as the build step to compile C/++ code and bundle it into a .deb
Steps:
Result:
Build failed during initialize Job step
Expected result:
Successfully start build
See the following for more information:
build_agent_success_log.txt
Direct_system_log.txt
build_agent_error_log.txt
Versions
Azure Devops Version 4.248.0 Ubuntu 22.04
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
No response
Version controll system
No response
Relevant log output
The text was updated successfully, but these errors were encountered: