Prabhatkumar59
Prabhatkumar59
Hi @Khacduy618 - Since we haven't heard back, we'll assume your issue is resolved and will close this issue for now. Feel free to reach out to us for any...
Hi @bnoordhuis - Thank you for bringing this issue to our attention. We will look into this issue and will update you on this issue after investigating.
Hi @bnoordhuis - Thanks for your input! So, just to confirm, is it working fine for you and your issue got resolved?
Hi @bnoordhuis- Thanks for your reply! I will check and update you for "invoking cl.exe". You are referring this original report- https://github.com/actions/runner-images/issues/6205 correct?
Thanks @bnoordhuis your reply. I will check and update for "invoking cl.exe".
Hi @bnoordhuis - As per your issue description, i can summarise that invoking **cl.exe** is overly complicated and not easy though. Despite finding a workaround using **vs-shell**, the core challenge...
Hi @bnoordhuis - Since we haven't heard back, we'll assume your issue is resolved and will close this issue for now. Feel free to reach out to us for any...
Hi @hzxuzhonghu - Thank you for bringing this issue to our attention. We will look into this issue and will update you after investigating.
Hi @vorporeal - For above mentioned issue, -Firstly, you can try to set permissions on $GITHUB_OUTPUT before entering the container. You can do this by running a chmod command to...
Hi @vorporeal - Really thanks for your input! We are closely checking into the details provided above https://github.com/actions/runner-images/issues/10915#issuecomment-2542259255 and will update you soon.