Hi Chris & Marek,
Thank you for solving the problem. BTW, do we have to restart biodb2
pygr.Data server using new pygr metabase?

Namshin Kim





On Thu, Mar 26, 2009 at 11:06 AM, Christopher Lee <l...@chem.ucla.edu>wrote:

>
> Once again, the megatest scripts are using old non-public interfaces
> for trying to control pygrdatapath and cache clearing.  We need to
> replace those with the new public interfaces and everything should
> work fine.  I am about to test that.
>
> -- Chris
> On Mar 25, 2009, at 6:29 PM, Marek Szuba wrote:
>
> >
> > Hi again,
> >
> > Another thing, this time related to dm2_download_megatest: if you
> > replace 'pygr.Data.getResource.addResourceDict' with
> > 'pygr.Data.addResourceDict' in line 57 of
> > pygr/apps/catalog_downloads.py, the test passes the point which caused
> > the previous error but fails in a different way:
> >
> > [...]
> > Download done.
> > gunzipping /tmp/test21671/dm2_multiz9way.txt.gz...
> > Saving NLMSA indexes from textdump /tmp/test21671/dm2_multiz9way.txt
> > Saving NLMSA binary index: 0  NLMSA_LPO_Internal      0       165964729
> > ...
> > Saving NLMSA binary index: 1  NLMSA_UNION_Internal    1       1847310997
> > ...
> > Traceback (most recent call last):
> >  File "protest.py", line 123, in <module>
> >    if do_test(sys.argv[2],sys.argv[3],sys.argv[4]):
> >  File "protest.py", line 33, in do_test
> >    m()
> >  File "/result/aqq/pygr/tests/oldtests/dm2_download_megatest.py",
> > line 50, in download_test
> >    pygrData.save() # save the built resources
> >  File "/result/aqq/pygr/build/lib.linux-x86_64-2.5/pygr/
> > metabase.py", line 729, in commit
> >    self.get_writer().saver.save_pending()
> >  File "/result/aqq/pygr/build/lib.linux-x86_64-2.5/pygr/
> > metabase.py", line 1039, in save_pending
> >    raise PygrDataEmptyError('there is no data queued for saving!')
> > pygr.metabase.PygrDataEmptyError: there is no data queued for saving!
> >
> > --
> > MS
> >
> >
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"pygr-dev" group.
To post to this group, send email to pygr-dev@googlegroups.com
To unsubscribe from this group, send email to 
pygr-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/pygr-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to