On Thu, Jul 23, 2009 at 10:43:49AM -0700, Marek Szuba wrote: -> On Wed, 22 Jul 2009 14:14:21 -0700 -> "C. Titus Brown" <[email protected]> wrote: -> -> > I would like to have someone (you?) pick the dates well in advance, -> > and then we can just stick to 'em, barring major bugs. -> -> Makes sense... I guess we'll add the dates to the roadmap wiki, too.
ok, thanks, that would help me keep things straight! -> > buildbot is client-server so we can certainly include a buildbot view -> > of the megatest results, with the buildslave running at UCLA. Let me -> > know if you want to try this out and we can help you configure etc. -> -> That would be pretty useful, in my view! Yesterday I installed (from -> source) all the required Python versions and Pygr dependencies on the -> megatest machine and the files required by megatests are already there, -> so I guess we can now proceed to setting up a buildslave. Yep! Contact Owen Pierce <[email protected]> directly and ask him to add a buildslave entry into the server for you; he should be able to help you out with specific buildslave settings as well. Let's start with 'echo hello, world' and move on from there ;) -> By the way, I've run standard tests on that box with different Python -> versions and there are issues with 2.3 - the bsddb module cannot be -> imported (it is there but the underlying shared library hasn't been -> built for some reason), moreover one of the tests fails: [ ... ] The bsddb problem is something I ran into; I had to jump through some hoops to get it to compile on 2.3. Ping me if you have trouble and I'll track down exactly what I did. -> ====================================================================== -> FAIL: test_seqInfoDict (seqdb_test.PrefixUnionDict_Test) -> ---------------------------------------------------------------------- -> Traceback (most recent call last): -> File "/tmp/pygr/tests/seqdb_test.py", line 650, in test_seqInfoDict -> assert (ii1.id, ii1.db) == (s1i.id, s1i.db) -> AssertionError -> -> I recall your set-up also suffered from initial problems with 2.3, does -> any of this look familiar? If I have to work on fixing this, I'd like to -> make sure it is not a known problem. This second problem is odd and doesn't smell like a 2.3 issue. Can I give you an account on lyorn, our Linux server? Then you can try running things with our python2.x installs, too. Just let me know off-list what username you prefer. cheers, --titus -- C. Titus Brown, [email protected] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en -~----------~----~----~----~------~----~------~--~---
