On Mon, Jul 29, 2013 at 2:49 PM, Peter Cock wrote:
> Hi Dave,
>
> Did a Trello card get filled for this problem of failing tests on the Tool
> Shed?
>
> Thanks,
>
> Peter
For anyone following this issue, on another thread Dave just replied:
> Peter,
>
> The issue with seq_rename incorrectly fai
Hi Dave,
Did a Trello card get filled for this problem of failing tests on the Tool Shed?
Thanks,
Peter
On Tue, Jun 11, 2013 at 9:04 AM, Björn Grüning wrote:
>
> Hi,
>
> I also have that error in the latest toolshed:
>
> AssertionError: Attempting to set field 'topology' to value '['-c']' in
>
Hi,
I also have that error in the latest toolshed:
AssertionError: Attempting to set field 'topology' to value '['-c']' in
form 'tool_form' threw exception: multiple matches to value/label "c" in
list control control: If the above
control is a DataToolparameter whose data type class does not inc
Peter,
That test output does look wrong, but wrong in a way that suggests a new
issue has been uncovered. I'll work on tracking it down as soon as I can.
--Dave B.
On 5/16/13 11:05:56.000, Peter Cock wrote:
On Thu, May 9, 2013 at 6:59 PM, Dave Bouvier mailto:d...@bx.psu.edu>> wrote:
On Thu, May 9, 2013 at 6:59 PM, Dave Bouvier wrote:
> Peter,
>
> As of my latest commit, the automated test results should now match that
> of run_functional_tests.sh.
>
>--Dave B.
>
>
Hi Dave,
This problem seems to have returned since then (unless this time
instead of missing test output I'
Buildbot can be triggered here
http://buildbot.g2.bx.psu.edu/builders/central-py2.7-linux-x86_64-postgres
manually
I think.
On Fri, May 10, 2013 at 10:56 PM, Greg Von Kuster wrote:
> Is there a more optimal time to initiate this testing process to better
> accommodate those in other time zones
Is there a more optimal time to initiate this testing process to better
accommodate those in other time zones? If anyone is waiting for the nightly
test results, we should tweak cron so no waiting is necessary (if possible).
On May 10, 2013, at 8:53 AM, Dave Bouvier wrote:
> That is correct,
That is correct, the tests are run nightly, some time after midnight
eastern US time, unless I manually initiate the testing process.
--Dave B.
On 5/10/13 05:36:41.000, Peter Cock wrote:
On Thu, May 9, 2013 at 6:59 PM, Dave Bouvier wrote:
Peter,
As of my latest commit, the automated test
On Thu, May 9, 2013 at 6:59 PM, Dave Bouvier wrote:
> Peter,
>
> As of my latest commit, the automated test results should now match that of
> run_functional_tests.sh.
>
>--Dave B.
Thanks Dave,
Presumably once the Test Tool Shed is updated, all the old tests will be re-run,
and so I should s
Peter,
As of my latest commit, the automated test results should now match that
of run_functional_tests.sh.
--Dave B.
On 5/9/13 06:06:16.000, Peter Cock wrote:
On Thu, May 9, 2013 at 10:59 AM, Peter Cock wrote:
On Thu, May 9, 2013 at 10:49 AM, Peter Cock wrote:
Hi Dave,
As you hope
Peter,
I have duplicated this discrepancy in my local environment, and will be
looking into the cause. I hope to have it resolved in short order.
--Dave B.
On 5/9/13 06:06:16.000, Peter Cock wrote:
On Thu, May 9, 2013 at 10:59 AM, Peter Cock wrote:
On Thu, May 9, 2013 at 10:49 AM, Pete
On Thu, May 9, 2013 at 10:59 AM, Peter Cock wrote:
>
> On Thu, May 9, 2013 at 10:49 AM, Peter Cock wrote:
> >
> > Hi Dave,
> >
> > As you hoped, these test now shows up on the tool page (as expected
> > they are test failures - apparently my install script isn't quite right
> > yet):
> >
> > ...
On Thu, May 9, 2013 at 10:49 AM, Peter Cock
wrote:
>
> Hi Dave,
>
> As you hoped, these test now shows up on the tool page (as expected
> they are test failures - apparently my install script isn't quite right
yet):
>
> ...
>
> This one is more interesting, and appears to be a problem with the
> t
13 matches
Mail list logo