Hi Marek, Namshin,
this dm2_download_megatest code is incorrect. It should not try to
save() after building, because building is supposed to have saved its
results automatically. The error message correctly indicates that
nothing is queued, presumably because the automatic save ran exactly
as it should have.
I modified the test code and waiting for it finish running.
-- Chris
On Mar 25, 2009, at 6:29 PM, Marek Szuba wrote:
>
> 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!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
