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

Update to Bones 0.5.1 #251

Merged
merged 3 commits into from
Oct 30, 2019
Merged

Update to Bones 0.5.1 #251

merged 3 commits into from
Oct 30, 2019

Conversation

tbekolay
Copy link
Member

Mostly, this commit modifies hardware.sh.template to use the new test-remote.sh template. This simplifies it a bit, and includes the new method of cleaning up the /tmp directory.

I confirmed that the /tmp directory clean up works. The script is set up to leave the most recent 3 directories, which it did successfully on the last run.

This depends on nengo/nengo-bones#65, so a Nengo Bones release will have to happen before this is merged. This PR also blocks all other PRs since it changes some of the values stored privately in TravisCI.

If possible, one thing I would still like to do in this PR is do a similar cleanup of conda environments, so that rather than cleaning up the conda environment for the given build, we remove all but the most recent three build environments. I'll start working on that, but since this works properly, we can start reviewing the Bones PR in the meantime.

Copy link
Member

@drasmuss drasmuss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good

tbekolay and others added 3 commits October 30, 2019 11:51
Mostly, this commit modifies hardware.sh.template to use the new
remote.sh template. This simplifies it a bit, and includes
the new method of cleaning up the /tmp directory.
Since it is no longer supported in default channel
@drasmuss drasmuss merged commit 4b56bb1 into master Oct 30, 2019
@drasmuss drasmuss deleted the update-hardware branch October 30, 2019 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants