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

Program times out. #25

Closed
mattpul opened this issue May 5, 2014 · 4 comments
Closed

Program times out. #25

mattpul opened this issue May 5, 2014 · 4 comments

Comments

@mattpul
Copy link
Contributor

mattpul commented May 5, 2014

Running test 24: spawn.J
Spawn location for J
---- sending commands ----
cJPq
---- awaiting results ----
Test 24 failed:

Program times out and does not return 'actual output' and 'expected output'. This is not the only occurrence, it happens for other tests as well.

@tangentstorm
Copy link
Contributor

This error is saying your implementation isn't halting properly when testris tries to run it. Perhaps your 'q' command is broken.

@raylu
Copy link
Contributor

raylu commented May 5, 2014

Or you're running under python3 and haven't pulled in 647916e from 2 weeks ago.

@mattpul
Copy link
Contributor Author

mattpul commented May 6, 2014

My suggestion is, even if the test fails or times out, it should still print the 'expected output' and the 'description'.
..............................................................................................................
Expected Output:
The matrix with the spawned block.

Description:
Spawn location for J
Here's the spawn location for J.

Notice that there are no spaces between the commands
this time. We said earlier that commands may be separated
by spaces or newlines, but we never said they had to be.
..............................................................................................................
So that the individual who is working on the test. knows what they are working towards.

Possibly also a message explaining what 'program timed out' means and what to do next (such as, error in code, go over it again).

@tangentstorm
Copy link
Contributor

(moving this conversation to #28 so i can close the original issue)

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

No branches or pull requests

3 participants