-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
Test example applications and rllib in jenkins tests. #707
Conversation
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
test this please |
Merged build finished. Test FAILed. |
Test FAILed. |
Merged build finished. Test FAILed. |
Test FAILed. |
btw, when the test ran this morning (https://amplab.cs.berkeley.edu/jenkins/job/Ray-PRB/1198/), it hung and left myriad zombie processes on the worker:
this is, um, suboptimal and really bad as the only way to recover is a hard reboot of the server. it can also affect other builds from different projects from running on the same machine... a clipper PRB build that fired off immediately after these zombies appeared hung indefinitely, and i discovered these zombies during my investigations for them. |
Thanks @shaneknapp, it looks like there may have been some corruption in the local scheduler. Or maybe the problem is something else. I'll see if I can reproduce it locally. |
Merged build finished. Test FAILed. |
Test FAILed. |
yep, it did it again on amp-jenkins-staging-worker-02.amp.
please try and reproduce and fix locally before doing more jenkins tests...
i'm heading out for the weekend and won't be in until late sunday.
…On Fri, Jul 7, 2017 at 4:09 PM, UCB AMPLab ***@***.***> wrote:
Merged build finished. Test FAILed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#707 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABiDrNrNupoCiu4uTowb9fYHR1lflzm7ks5sLrqVgaJpZM4ONXlt>
.
|
Merged build finished. Test PASSed. |
Test PASSed. |
# --iterations=2 | ||
|
||
docker run --shm-size=10G --memory=10G $DOCKER_SHA \ | ||
python /ray/python/ray/rllib/evolution_strategies/example.py \ |
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.
Maybe set --env-name as well here? We could also run rllib/train.py instead, which somewhat supercedes the example.py files.
Otherwise this looks good to me.
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.
Fixed. I agree switching to rllib/train.py would be a good change, perhaps in a subsequent PR, to make things more uniform.
Merged build finished. Test PASSed. |
Test PASSed. |
This currently tests A3C and evolution strategies in CI. For some reason the policy gradient example doesn't seem to work in Docker.
This should address #558.