Peter, Correction: I mistakenly thought your email was regarding a repository on the main tool shed, against which I manually ran the test framework. Now that I noticed that you're referring to a repository on the test tool shed, the 13:10 test result is because the test tool shed's test run took 23 hours to complete. The explanation for the 16:16 test result remains correct. --Dave B. On 02/21/2014 10:26 AM, Dave Bouvier wrote:
Peter,
The test result at 13:11:20 is due to me manually running the install and test framework to test the fabric replacement code I introduced. The test result at 16:16:58 is due to the repository preparation script running successfully at its scheduled time, initializing the tool test results for the soon-following test run, but the install and test framework failed to run any tests due to a missing import in 12566:01a572fb8b4c. I've committed a fix for that issue now, and this evening's test run should return proper results.
--Dave B.
On 02/21/2014 04:37 AM, Peter Cock wrote:
Hi Greg & Dave,
Now that moving symlinks has been fixed, something new happened on the MIRA4 tests yesterday: http://testtoolshed.g2.bx.psu.edu/view/peterjc/mira4_assembler
It seems one test run has been split in two - the early section at 13:11:20 includes the tests run for mira_4_0_de_novo and mira_4_0_bait (which passed - yay), while the later section at 16:16:58 reported that mira_4_0_mapping has no tests (true for now).
Peter
--
Automated tool test results
Test runs 2014-02-20 16:16:58 Automated test environment Tools missing tests or test data *Tool id:* mira_4_0_mapping *Tool version:* 0.0.2 *Tool guid:* testtoolshed.g2.bx.psu.edu/repos/peterjc/mira4_assembler/mira_4_0_mapping/0.0.2
<http://testtoolshed.g2.bx.psu.edu/repos/peterjc/mira4_assembler/mira_4_0_mapping/0.0.2>
*Missing components:* Functional test definitions missing for mira_4_0_mapping.
2014-02-20 13:11:20 Automated test environment Tests that passed successfully *Tool id:* mira_4_0_bait *Tool version:* mira_4_0_bait *Test:* test_tool_000000 (functional.test_toolbox.TestForTool_testtoolshed.g2.bx.psu.edu/repos/peterjc/mira4_assembler/mira_4_0_bait/0.0.1
*Tool id:* mira_4_0_bait *Tool version:* mira_4_0_bait *Test:* test_tool_000001 (functional.test_toolbox.TestForTool_testtoolshed.g2.bx.psu.edu/repos/peterjc/mira4_assembler/mira_4_0_bait/0.0.1
*Tool id:* mira_4_0_bait *Tool version:* mira_4_0_bait *Test:* test_tool_000002 (functional.test_toolbox.TestForTool_testtoolshed.g2.bx.psu.edu/repos/peterjc/mira4_assembler/mira_4_0_bait/0.0.1
*Tool id:* mira_4_0_de_novo *Tool version:* mira_4_0_de_novo *Test:* test_tool_000000 (functional.test_toolbox.TestForTool_testtoolshed.g2.bx.psu.edu/repos/peterjc/mira4_assembler/mira_4_0_de_novo/0.0.2
Successful installations Repository dependencies/- installation of these additional repositories is required/ Tool dependencies
___________________________________________________________ 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: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
___________________________________________________________ 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: http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/