Closed jwikman closed 2 years ago
Hi,
Many thanks for raising this issue. Unfortunately we have not been able to get to this issue as soon as we'd have liked. Since it has been a long time since this issue was last updated, it is possible that this has been fixed by a newer release of Business Central and the AL extension for Visual Studio Code. We have thus decided to close it.
If the issue still affects you on the latest insider build of Business Central, please help us and open a new issue for us with the latest steps to reproduce the issue, and link back to this closed issue to track any comments or discussions.
Thanks,
Thaddeus
I have not seen this error in quite some time, so I believe that it is actually resolved. 👍
Describe the bug Now and then (not often at all) when compiling we get the error System.IO.IOException: The process cannot access the file '[path to my g.xlf file]' because it is being used by another process. When running locally you just try again and it works. But when this happens in a pipeline, it fails the pipeline causing som extra work for investigating the fail. Rerunning the pipeline always works...
I could implement a retry logic in our pipelines (or @freddydk could do this in Compile-AppInBcContainer ;-)) , but I rather see this being fixed in the compiler.
To Reproduce This is not happening very often, so there is no clean repro.
Below is the output in my pipeline, where you see the call to alc.exe that fails
Expected behavior The compilation should not fail with this error. If the file is locked (by the alc process itself, or could it be a AV scanning the file?) the compiler could wait for the file to be released...
Screenshots N/A
5. Versions: Microsoft (R) AL Compiler version 6.1.5.24898