On Wed, Apr 24, 2013 at 10:12 AM, Peter Cock p.j.a.c...@googlemail.com wrote:
..., I've still finding some other cases where despite having
tests defined, nothing shows up on the Tool Shed test results page.
Here's an example where I see that two tools (promoter2 and
wolf_psort) have no
Hi Dave,
On Thu, Apr 25, 2013 at 2:27 PM, Dave Bouvier d...@bx.psu.edu wrote:
Peter,
That is the intended behavior, but I've added a trello card
(https://trello.com/c/O9YmzUT4) for revisiting that decision at some point.
Is that the right Trello card? Is seems to be all about multiple tool
On Thu, Apr 25, 2013 at 4:25 PM, Dave Bouvier d...@bx.psu.edu wrote:
Peter,
Your point is well taken about the utility of the testing framework in the
tool development process. The framework has been modified as of
9520:41d8cdde4729 to only flag a changeset revision not to be tested if no
Peter,
I've committed a fix for this in 9480:a80175a97194, and re-run the
automated testing framework. However, as you will see, the test still
reports an error. This is not due to an issue in your repository, but an
problem on the Galaxy side, as described in the following trello card:
On Fri, Apr 19, 2013 at 4:46 PM, Dave Bouvier d...@bx.psu.edu wrote:
Peter,
I've committed a fix for this in 9480:a80175a97194, and re-run the automated
testing framework. However, as you will see, the test still reports an
error. This is not due to an issue in your repository, but an problem
On Tue, Apr 16, 2013 at 9:42 PM, Greg Von Kuster g...@bx.psu.edu wrote:
Hello Peter,
On Apr 15, 2013, at 11:04 AM, Peter Cock wrote:
The View tool functional test results option clearly lists failed tests,
but it is not obvious if there were any successful tests. Could that
be indicated
On Wed, Apr 17, 2013 at 9:44 AM, Peter Cock p.j.a.c...@googlemail.comwrote:
On Tue, Apr 16, 2013 at 9:42 PM, Greg Von Kuster g...@bx.psu.edu wrote:
Hello Peter,
On Apr 15, 2013, at 11:04 AM, Peter Cock wrote:
The View tool functional test results option clearly lists failed tests,
but
Hello Peter,
On Apr 15, 2013, at 11:04 AM, Peter Cock wrote:
The View tool functional test results option clearly lists failed tests,
but it is not obvious if there were any successful tests. Could that
be indicated somehow (e.g. five tests passed for tool xxx).
If I understand your
Peter,
The automated testing framework is also running against the test tool
shed. Could you send me a link to the repository that is behaving oddly?
--Dave B.
On 4/12/13 06:42:04.000, Peter Cock wrote:
Hi all,
I'd like to be able to experiment with the new automated testing
recently
On Mon, Apr 15, 2013 at 2:20 PM, Dave Bouvier d...@bx.psu.edu wrote:
Peter,
The automated testing framework is also running against the test tool shed.
Could you send me a link to the repository that is behaving oddly?
e.g. http://toolshed.g2.bx.psu.edu/view/peterjc/tmhmm_and_signalp
On the
Peter,
I'm unable to duplicate that behavior, the View tool functional test
results option shows up on the test tool shed both when I'm logged in
and logged out. My suggestion would be to clear your browser's cookies
and cache, and see if that makes a difference.
--Dave B.
On 4/15/13
On Mon, Apr 15, 2013 at 3:56 PM, Dave Bouvier d...@bx.psu.edu wrote:
Peter,
I'm unable to duplicate that behavior, the View tool functional test
results option shows up on the test tool shed both when I'm logged in and
logged out. My suggestion would be to clear your browser's cookies and
Hi all,
I'd like to be able to experiment with the new automated testing
recently added to the main Tool Shed http://toolshed.g2.bx.psu.edu/
by first trying my updates on the Test Tool Shed (to make sure my
tests will work before making the tool update public).
It appears that the testing
13 matches
Mail list logo