On Fri, 2010-11-12 at 15:24 +0300, Dmitry wrote:
> On Fri, 12 Nov 2010 09:23:03 -0200, Lucas Meneghel Rodrigues 
> <[email protected]> wrote:
> > On Thu, 2010-11-11 at 21:56 +0300, Dmitry wrote:
> > > On Mon, 08 Nov 2010 16:55:10 -0200, Lucas Meneghel Rodrigues 
> > > <[email protected]> wrote:
> > > > On Mon, 2010-11-08 at 16:43 -0200, Eduardo Habkost wrote:
> > > > > Hi, all,
> > > > > 
> > > > > This is a note about the Autotest Git SVN mirror. I have just created 
> > > > > a
> > > > > "organization" account on github for the Autotest code, so the mirror
> > > > > doesn't need to live on my personal github account.
> > > > > 
> > > > > The new addresses for the repository are:
> > > > > 
> > > > > - git://github.com/autotest/autotest.git (git checkout)
> > > > > - https://[email protected]/autotest/autotest.git (http checkout)
> > > > > - https://github.com/autotest/autotest (web browsing)
> > > > > 
> > > > > If you a git 'remote' in your local git clone pointing to the old
> > > > > repository, you can simply update the remote URL on your .git/config
> > > > > file so git starts using the new address the next time you run 'git
> > > > > remote update'.
> > > > > 
> > > > > Someone with permissions in the wiki needs to update the following 
> > > > > pages
> > > > > to point to the new location:
> > > > > 
> > > > >  - http://autotest.kernel.org/wiki/GitWorkflow
> > > > >  - http://autotest.kernel.org/wiki/DownloadSource
> > > > 
> > > Today i've tried to deploy server from current, but without success.
> > > Seems like this is because incorrect db schema. Off course this is 
> > > possible when you dealing with "current".
> > > BTW can some one please post an last good commit.
> > 
> > I just tried to deploy a new server here and didn't have any problems.
> > Could you post your problem so we can troubleshoot it?
> I've tried to follow KVM's guide from here
>  http://www.linux-kvm.org/page/KVM-Autotest/Server_Install
> I've used FC12 
> and got following error
> Subject: monitor_db exception
> dws3.autotest / 829 / 12:27:48 11/11/10
> EXCEPTION: Uncaught exception; terminating monitor_db
> Traceback (most recent call last):
>   File "/usr/local/autotest/scheduler/monitor_db.py", line 164, in 
> main_without_exception_handling
>     dispatcher.tick()
>   File "/usr/local/autotest/scheduler/monitor_db.py", line 650, in tick
>     self._schedule_special_tasks()
>   File "/usr/local/autotest/scheduler/monitor_db.py", line 915, in 
> _schedule_special_tasks
>     for task in self._get_prioritized_special_tasks():
>   File "/usr/local/autotest/scheduler/monitor_db.py", line 908, in 
> _get_prioritized_special_tasks
>     return sorted(queued_tasks, key=task_priority_key)
>   File "/usr/lib/python2.6/site-packages/django/db/models/query.py", line 83, 
> in __len__
>     self._result_cache.extend(list(self._iter))
>   File "/usr/lib/python2.6/site-packages/django/db/models/query.py", line 
> 269, in iterator
>     for row in compiler.results_iter():
>   File "/usr/lib/python2.6/site-packages/django/db/models/sql/compiler.py", 
> line 672, in results_iter
>     for rows in self.execute_sql(MULTI):
>   File "/usr/lib/python2.6/site-packages/django/db/models/sql/compiler.py", 
> line 727, in execute_sql
>     cursor.execute(sql, params)
>   File "/usr/lib/python2.6/site-packages/django/db/backends/util.py", line 
> 15, in execute
>     return self.cursor.execute(sql, params)
>   File "/usr/lib/python2.6/site-packages/django/db/backends/mysql/base.py", 
> line 86, in execute
>     return self.cursor.execute(query, args)
>   File "/usr/lib64/python2.6/site-packages/MySQLdb/cursors.py", line 173, in 
> execute
>     self.errorhandler(self, exc, value)
>   File "/usr/lib64/python2.6/site-packages/MySQLdb/connections.py", line 36, 
> in defaulterrorhandler
>     raise errorclass, errorvalue
> OperationalError: (1054, "Unknown column 'host_queue_entries.id' in 'where 
> clause'")
> The only stupid guess I have that this is because of yum installed 
> Django-1.2.3-1.fc12 ,but according to release-notes 1.0.4 is required.
> Am i right?

Yes, that is the problem. For now, uninstall django from your fedora
install and let build_externals.py pick 1.0.4 for you. Sorry about that.

> Can you please post your versions or output from build_externals.py
> 
> Luckily today I've found another guide from fedora folks
> http://fedoraproject.org/wiki/Automate_AutoQA_clients_installation
> which works like charm, probably because they provides prepacked package
> with well defined deps, and this package require Django-1.0.4-1.fc13,
> 
> BTW can you please add that link to your wiki (i don't have enough
> permissions)

Sure thing! Remembering that autoqa is based on autotest 0.12.0 (I still
have to release 0.12.1).
 
> > > Main SVN server has stable branches (the most recent is 0.12.1)
> > > Are they really stable?
> > 
> > To the best of my knowledge, yes (well, I maintain those branches, and
> > have tested them a lot). They are lagging behind the current state of
> > latest git, obviously, but do work well.
> > 
> > > Do you have plans to push it to git-mirror?
> > 
> > No, once all the maintainers agree on moving autotest entirely to git,
> > we'll drop the github svn mirror, or perhaps making the current mirror
> > the 'official' source. Meanwhile, the git mirror is only for trunk.
> > 
> > > > Eduardo, thank you very much!
> > > > 
> > > > _______________________________________________
> > > > Autotest mailing list
> > > > [email protected]
> > > > http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
> > 
> > 
> > _______________________________________________
> > Autotest mailing list
> > [email protected]
> > http://test.kernel.org/cgi-bin/mailman/listinfo/autotest


_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest

Reply via email to