Fri, 13 Jun 2014 12:56:45 +0200 [test/migration] fix crash on execution
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 13 Jun 2014 12:56:45 +0200] rev 9792
[test/migration] fix crash on execution This assertion is there for unclear reasons. ===================== unittest_migration.py ======================= -> creating tables [====================] -> inserting default user and default groups. -> storing the schema in the database [====================] -> database for instance data initialized. F ====================================================================== FAIL: test_db_creation (unittest_migration.BaseCreationTC) make sure database can be created ---------------------------------------------------------------------- Traceback (most recent call last) File "/home/auc/confs/forges/logilab/common/testlib.py", line 661, in _proceed testfunc(*args, **kwargs) File "/home/auc/confs/forges/cubicweb/test/unittest_migration.py", line 106, in test_db_creation handler.build_db_cache() File "/home/auc/confs/forges/cubicweb/devtools/__init__.py", line 469, in build_db_cache self.init_test_database() File "/home/auc/confs/forges/cubicweb/devtools/__init__.py", line 729, in init_test_database init_repository(self.config, interactive=False) File "/home/auc/confs/forges/cubicweb/server/__init__.py", line 217, in init_repository repo = Repository(config, vreg=vreg) File "/home/auc/confs/forges/cubicweb/server/repository.py", line 197, in __init__ self.init_cnxset_pool() File "/home/auc/confs/forges/cubicweb/server/repository.py", line 220, in init_cnxset_pool config.bootstrap_cubes() File "/home/auc/confs/forges/cubicweb/devtools/__init__.py", line 176, in bootstrap_cubes super(TestServerConfiguration, self).bootstrap_cubes() File "/home/auc/confs/forges/cubicweb/server/serverconfig.py", line 279, in bootstrap_cubes self.init_cubes(self.expand_cubes(splitstrip(line))) File "/home/auc/confs/forges/cubicweb/cwconfig.py", line 1022, in init_cubes super(CubicWebConfiguration, self).init_cubes(cubes) File "/home/auc/confs/forges/cubicweb/cwconfig.py", line 798, in init_cubes assert self._cubes is None, repr(self._cubes) AssertionError: ('card', 'file', 'localperms', 'tag')
Thu, 05 Jun 2014 17:53:27 +0200 [web] Remove unreachable and broken code
Rémi Cardona <remi.cardona@logilab.fr> [Thu, 05 Jun 2014 17:53:27 +0200] rev 9791
[web] Remove unreachable and broken code
Tue, 15 Apr 2014 11:55:37 +0200 [testlib] call init_config once the config has been properly bootstraped
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 15 Apr 2014 11:55:37 +0200] rev 9790
[testlib] call init_config once the config has been properly bootstraped This should be done right after repository instantiation and as such involves giving CWTC.init_config as a callback to the test database handler (which will itself gives it to the repository initialization function). This unfortunatly requires to pass the init_config method to the server.init_repository function because it has to be called after the config has been initialized (which is done in Repository.__init__) but before the migration handler is instantiated (which will call 'server_maintainance' hook, hence may require the proper config). Another way to fix this would be to change the initialization sequence, but this is another story. Closes #3749378
Thu, 12 Jun 2014 17:50:50 +0200 [devtools] even better: use a plain Connection (server-side) object for pre_setup
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 12 Jun 2014 17:50:50 +0200] rev 9789
[devtools] even better: use a plain Connection (server-side) object for pre_setup The previous commit switched from passing a Session to a ClientConnection. This fixes unittest_ldapsource's pre_setup_database, which relied on a server-side object to get at the repo.
Fri, 30 May 2014 17:25:31 +0200 [devtools] pre_setup_database should take a connection object
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 30 May 2014 17:25:31 +0200] rev 9788
[devtools] pre_setup_database should take a connection object
Fri, 30 May 2014 11:10:54 +0200 [tests/migration] use the new connection api
Aurelien Campeas <aurelien.campeas@logilab.fr> [Fri, 30 May 2014 11:10:54 +0200] rev 9787
[tests/migration] use the new connection api
Wed, 28 May 2014 17:33:16 +0200 [tests/undo] use the new connection api
Aurelien Campeas <aurelien.campeas@logilab.fr> [Wed, 28 May 2014 17:33:16 +0200] rev 9786
[tests/undo] use the new connection api
Thu, 12 Jun 2014 14:10:02 +0200 [js/ajax] deprecate user-callback support
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 12 Jun 2014 14:10:02 +0200] rev 9785
[js/ajax] deprecate user-callback support Related to #3567793.
Fri, 07 Mar 2014 14:03:44 +0100 EditRelationMixIn: stop using user_rql_callback
Julien Cristau <julien.cristau@logilab.fr> [Fri, 07 Mar 2014 14:03:44 +0100] rev 9784
EditRelationMixIn: stop using user_rql_callback Add generic add_relation/delete_relation ajax functions and use those. Related to #3567793
Wed, 28 May 2014 17:57:40 +0200 [tests/storage] use the new connection api
Aurelien Campeas <aurelien.campeas@logilab.fr> [Wed, 28 May 2014 17:57:40 +0200] rev 9783
[tests/storage] use the new connection api
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip