Skip to content
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

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

Open
urbanishimwe opened this issue May 5, 2020 · 2 comments
Open

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

urbanishimwe opened this issue May 5, 2020 · 2 comments

Comments

@urbanishimwe
Copy link

@urbanishimwe urbanishimwe commented May 5, 2020

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

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 dmitshur added this to the Unreleased milestone May 5, 2020
@dmitshur
Copy link
Contributor

@dmitshur dmitshur commented May 5, 2020

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

@dmitshur dmitshur changed the title playground: provide different outputs on the same programs x/playground: exit code 2 is cached and returned for a valid program May 5, 2020
@urbanishimwe
Copy link
Author

@urbanishimwe urbanishimwe commented May 6, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants