x/playground: exit code 2 is cached and returned for a valid program

[urbanishimwe]

What version of Go are you using (go version)?

$ go version
go1.14.2

Does this issue reproduce with the latest release?

Probably yes

What operating system and processor architecture are you using (go env)?

playground configurations

What did you do?

I changed the syntax of two programs(that are logically the same), by switching the order of the functions

• https://play.golang.org/p/ftthvh6ifYd
• https://play.golang.org/p/mn1PAI19xI6

What did you expect to see?

I was expecting to see the same outputs

What did you see instead?

The second program(from the above list) crashed

[dmitshur]

For the second program, it looks like a bad execution was cached. If you modify it slightly (e.g., add some trailing whitespace on one of the lines) and run it again, it works the same as the first program.

Do you remember when you created and ran that second playground program for the first time? There have been various improvements to the playground as part of #25224 recently, so this might be related to that.

/cc @toothrot @cagedmantis

[urbanishimwe]

For the second program, it looks like a bad execution was cached. If you modify it slightly (e.g., add some trailing whitespace on one of the lines) and run it again, it works the same as the first program.

Do you remember when you created and ran that second playground program for the first time? There have been various improvements to the playground as part of #25224 recently, so this might be related to that.

/cc @toothrot @cagedmantis

When you slightly modify the program it works! I ran the second program the day before I posted this issue.