Hi Peter,

Thanks for the bug report. It looks like if requests is available to
the framework these unicode errors go away (it doesn't have to fall
back on my poor attempt to provide a similar interface).


I'll create a Trello card and try to add an egg for this - other
developers on the team have likewise said they would like a requests
dependency available in the past so I doubt there will be objections.



It looks like the ftype changeset has already caught some errors (your
sample_seqs tool only produces fasta outputs but some outputs are
labelled as sff):


On Tue, Mar 18, 2014 at 6:46 AM, Peter Cock <p.j.a.c...@googlemail.com> wrote:
> On Fri, Mar 14, 2014 at 8:36 PM, John Chilton <jmchil...@gmail.com> wrote:
>> Hello Tool Developers,
>> Haven't known when to send this out, but I figure since you haven't
>> received any e-mail from me today it might be a good time.
>> tl;dr - Tool functional tests experienced a significant overhaul over
>> the last release and will continue to change over the next couple
>> releases, but in a backward compatible so hopefully you will not need
>> to care unless you want to.
>> ...
> Thank you John for this detailed report - I knew bits and pieces
> from prior discussions, but still found this recap very useful.
> I'm now taking advantage of the new environment variable to test
> with both GALAXY_TEST_DEFAULT_INTERACTOR=api (the new
> (the old framework) under TravisCI, see:
> https://github.com/peterjc/galaxy_blast/commit/b9db5c9edc57314c5ab4122bce0b00fa2f9cfb94
> https://github.com/peterjc/pico_galaxy/commit/ceed9e0698989b7a617d75d6c483fa28ae61b333
> http://blastedbio.blogspot.co.uk/2013/09/using-travis-ci-for-testing-galaxy-tools.html
> http://lists.bx.psu.edu/pipermail/galaxy-dev/2014-March/018677.html
> The BLAST+ tests are fine both ways, but there appears to be a
> unicode issue with the API based testing of pico_bio (twill is fine):
> https://travis-ci.org/peterjc/pico_galaxy/builds/21008616
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xbe in position
> 847: ordinal not in range(128)
> Thanks,
> Peter
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:

To search Galaxy mailing lists use the unified search at:

Reply via email to