Bug #4270: schema_update.py FAILS to work - Appion - Electron Microscopy Group

Actions

Copy link

Bug #4270

open

schema_update.py FAILS to work

Added by Neil Voss about 8 years ago. Updated about 8 years ago.

Status:

Assigned

Priority:

Low

Assignee:

Neil Voss

Category:

Target version:

Start date:

06/30/2016

Due date:

% Done:

Estimated time:

Affected Version:

Appion/Leginon 3.2

Show in known bugs:

Workaround:

Description

connected to db 'projectdb' on server 'localhost'
SVN checkout revision is 19880
CUSTOM:   SELECT value FROM `install` WHERE `key`='revision' 
Database recorded revision is 18367
CUSTOM:   SELECT value FROM `install` WHERE `key`='version' 
SVN checkout revision is 19880
Traceback (most recent call last):
  File "./schema_update.py", line 13, in <module>
    schema_revisions = updatelib_inst.getBranchUpdateRevisionSequence()
  File "/home/appionuser/dbschema/updatelib.py", line 110, in getBranchUpdateRevisionSequence
    db_update_sequence = self.getUpdateRevisionSequence(self.db_branch)
  File "/home/appionuser/dbschema/updatelib.py", line 47, in getUpdateRevisionSequence
    raise "Unknown svn branch" 
TypeError: exceptions must be old-style classes or derived from BaseException, not str

Any ideas on why this is happening? This is for my docker with a fresh install of the latest CentOS 6, I tried myami beta, trunk, and 3.2 all give the same error.

Actions

Copy link

Updated by Anchi Cheng about 8 years ago

Assignee changed from Anchi Cheng to Neil Voss

dbschema/updatelib.py getUpdateRevisionSequence has an input of svn_branch. It is unfortunately not printed. Could you check what that gives ? The error is caused by it not matching any of the cases and then a bad exception raised.

Actions

Copy link

Updated by Neil Voss about 8 years ago

added

print svn_branch

Getting release revision from /emg/sw/myami/myamiweb/xml/projectDefaultValues.xml
Release revision is 19429
myami-pre3.3
Traceback (most recent call last):
  File "./schema_update.py", line 13, in <module>
    schema_revisions = updatelib_inst.getBranchUpdateRevisionSequence()
  File "/emg/sw/myami/dbschema/updatelib.py", line 110, in getBranchUpdateRevisionSequence
    checkout_update_sequence = self.getUpdateRevisionSequence(self.checkout_branch)
  File "/emg/sw/myami/dbschema/updatelib.py", line 48, in getUpdateRevisionSequence
    raise "Unknown svn branch" 
TypeError: exceptions must be old-style classes or derived from BaseException, not str

We are looking at ''myami-pre3.3'' I found another problem which maybe the cause:

myami] svn up
svn: The path '.' appears to be part of a Subversion 1.7 or greater
working copy rooted at '/emg/sw/myami'.
Please upgrade your Subversion client to use this working copy.

I think my svn checkout is being done by my mac (svn, version 1.9.3) and then the update is being done by the centos 6 (svn, version 1.6.11). Maybe git will fix my problems. :)

centos6 has git version 1.7.1 and my mac has git version 2.9.0 though, so probably a whole new set of problems.

Actions

Copy link

Updated by Neil Voss about 8 years ago

I tested this again in docker using the same versions of subversion and it still fails.

Interestingly it is running getUpdateRevisionSequence twice.

SVN checkout revision is 19939
CUSTOM:   SELECT value FROM `install` WHERE `key`='revision' 
Database recorded revision is 18367
CUSTOM:   SELECT value FROM `install` WHERE `key`='version' 
SVN checkout revision is 19939
svn_branch trunk
svn_branch myami-3.3
Traceback (most recent call last):
  File "./schema_update.py", line 13, in <module>
    schema_revisions = updatelib_inst.getBranchUpdateRevisionSequence()
  File "/emg/sw/myami/dbschema/updatelib.py", line 111, in getBranchUpdateRevisionSequence
    db_update_sequence = self.getUpdateRevisionSequence(self.db_branch)
  File "/emg/sw/myami/dbschema/updatelib.py", line 48, in getUpdateRevisionSequence
    raise "Unknown svn branch" 
TypeError: exceptions must be old-style classes or derived from BaseException, not str

Actions

Copy link