-
Notifications
You must be signed in to change notification settings - Fork 0
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
Sheep compatiability #21
Conversation
Running this branch on my pi produces this error when the start button is pressed in the editor:
The later run request gives a 409
The output of running pytest is
It looks like the failures are also due to the directory |
Fixed and tested on fresh install |
This is correct. This is the folder where the usercode which is to be run in the next round is uploaded to. It is now automatically created by shepherd. Logs aren't done in this pr but you can see that the code works by looking |
Ah so |
Correct :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From running the tests:
test/test_editor.py .. [ 20%]
test/test_home.py . [ 30%]
test/test_runner.py xF.. [ 70%]
test/test_upload.py .FF [100%]
test_start
fails at line 20 due to a timeout. Looks like it comes from this line:
type(runner).state.__set__(runner, States.RUNNING)
Why is it like this? In fact all of the rest of the tests fail due to this.
I've just tried changing this: Line 33 in 18c9b54
to this: runner.state = States.RUNNING and all tests pass apart from |
This test looks at the logs and checks they are as they should be. However if shepherd crashes in this test then the usercode continues running and continues writing to the logs. This commit uses context managers to harden against this but does not completely solve the problem
This test looks at the logs and checks they are as they should be. However if shepherd crashes in this test then the usercode continues running and continues writing to the logs. This commit uses context managers to harden against this but does not completely solve the problem
…d-2 into sheep-compatiability
@fenjalien ready for another round of review |
You can still retroactively do the code review but we need to move fast |
This PR will be merged when there is all of the parts which sheep needs to run working.