Causing "##[error]No such file or directory" for later "run" steps about setup-go

[yousong]

Hey @yousong We have an item open for this issue here: actions/runner#169

Note sure if it's because of redirection, but definitely it's not powershell. So likely the issue is different.

You can workaround it by separating out the multi-line step into individual steps, as it appears you have done in your repo!

I compacted all shell run steps into into a single one. Not spliting them into individual steps.

Note that the issue reported here is that 2nd and later shell run steps fail

[thboop]

Hey @yousong , I apologize I misread your issue.

I forked your repo and was able to reproduce the issue!

The runner is actually throwing an error because the folder it expects to find is missing. If you change your line here to cp -r instead of mv the following steps should execute.

You can see my example here

That being said, if you don't need to use that directory for your workflow to work, you may want to consider using the current working directory to slightly speed up your actions!

[yousong]

Tried v1 and v1.1.1, the issue persists

[yousong]

Friendly ping

[bryanmacfarlane]

Doesn't seem like a setup-go issue but @thboop can have a look.

[thboop]

Hey @yousong We have an item open for this issue here: actions/runner#169

You can workaround it by separating out the multi-line step into individual steps, as it appears you have done in your repo!

[yousong]

Hey @yousong , I apologize I misread your issue.

I forked your repo and was able to reproduce the issue!

The runner is actually throwing an error because the folder it expects to find is missing. If you change your line here to cp -r instead of mv the following steps should execute.

You can see my example here

I see. It's working directory "not found" because I moved it to another place.

That being said, if you don't need to use that directory for your workflow to work, you may want to consider using the current working directory to slightly speed up your actions!

This is specific to the golang code and the container image in use here. The code needs to sit in $GOPATH and we tend to set it to $HOME/go. $GOPATH has its own directory structure.

Anyway, thanks for your time and efforts. Appreciate it

Good day ;)