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

Running lamachine-update.sh sometimes fails with weird syntax error, but upon rerunning everything is fine #21

Closed
proycon opened this issue Feb 21, 2017 · 4 comments
Assignees
Labels

Comments

@proycon
Copy link
Owner

proycon commented Feb 21, 2017

I often find that the virtualenv lamachine-update.sh fails with a strange syntax error. I wonder if it might be caused by the running script being updated whilst it runs? Isn't it entirely in memory yet?

Simply rerunning lamachine-update.sh after this error always fixes it.

--------------------------------------------------------
Updating LaMachine itself (branch: master)
--------------------------------------------------------
/scratch2/www/lamachine/src/LaMachine
Already on 'master'
Your branch is up-to-date with 'origin/master'.
remote: Counting objects: 3, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 3 (delta 0), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (3/3), done.
From https://github.com/proycon/LaMachine
   9686aa0..19ca62f  master     -> origin/master
Updating 9686aa0..19ca62f
Fast-forward
 virtualenv-bootstrap.sh | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)
/scratch2/www/lamachine/bin/lamachine-update.sh: line 783: syntax error near unexpected token `('
/scratch2/www/lamachine/bin/lamachine-update.sh: line 783: `echo "Updating LaMachine itself (branch: $BRANCH)"
@proycon proycon added the bug label Feb 21, 2017
@proycon proycon self-assigned this Feb 21, 2017
proycon added a commit that referenced this issue Mar 3, 2017
@proycon
Copy link
Owner Author

proycon commented Mar 3, 2017

that seemed to work? not sure why though

proycon added a commit that referenced this issue Mar 4, 2017
@proycon
Copy link
Owner Author

proycon commented Mar 6, 2017

Should be solved now

@proycon proycon closed this as completed Mar 6, 2017
@proycon
Copy link
Owner Author

proycon commented Apr 6, 2017

It's not solved... still occurs regularly...

@proycon proycon reopened this Apr 6, 2017
proycon added a commit that referenced this issue Apr 7, 2017
@proycon
Copy link
Owner Author

proycon commented Feb 14, 2018

haven't seen this in a while

@proycon proycon closed this as completed Feb 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant