Hi again, As you probably remember, one of the purposes of rewriting the download megatest has been to have it use dedicated metabases rather than worldbase. It turns out however the two interact with each other - or to be exact, individual metabases appear to be tied to worldbase - in a sometimes peculiar manner. And I'm not even talking about downloading and building NLMSAs being controlled controlled by $WORLDBASExxx environment variables even when individual metabases are used - it gets more interesting...
Take a machine running the new download megatest, with my stupid httpdPort bug already fixed. The test repeatedly and reproducibly runs without errors. At some point, the UCLA XML-RPC server stops responding to requests. This should have no effect on the new version of the test, right? Except what really happens is: - the text file is downloadad and unpacked; - after beginning to save indexes (i.e. after it has been announced but before the message about index 0 is displayed), a warning appears about problems talking to the UCLA XML-RPC server; - "No Test.NLMSA found in WORLDBASEPATH". What do you think, guys? Is it a bug in the megatest or something in Pygr code itself worth looking into? Cheers, -- 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-...@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.
