boolean testing problems
Hi, I really appreciate your help with this, and I'm sorry to keep bothering you about the boolean thing, but: It seems the recent successive changes to the boolean parameter are conflicting with one another (some changes made to the testing framework and others to the rest of galaxy). At changeset 3402:bb50ac713feb (before the whole boolean issue start), testing "gpos_concat_1" works OK - single tests the succeeds (and only tests the "true" case). At changeset 3410:4a416d872806 (which fixed the boolean in the testing framework), testing "gpos_concat_1" works OK - with two tests, checking both "true" and "false" cases. But changeset 3411:0c07212afc00 (which fixed the boolean bug not related to testing framework) broke the testing framework entirely: testing "gpos_concat_1" fails on both tests (together with all my tools which have a boolean parameter, even if those tests worked before). -gordon
And another small boolean-related issue: If the tool has a checkbox that is "true" by default (e.g. the "Operate on Genomic Intervals -> Concatenate" tool), Then regardless of the boolean setting used to run the job, clicking on "ReRun" will show the checkbox as selected. If the tool as a checkbox that is "false" by default, re-run will show the correct state based on what was executed. -gordon Assaf Gordon wrote:
Hi,
I really appreciate your help with this, and I'm sorry to keep bothering you about the boolean thing, but:
It seems the recent successive changes to the boolean parameter are conflicting with one another (some changes made to the testing framework and others to the rest of galaxy).
At changeset 3402:bb50ac713feb (before the whole boolean issue start), testing "gpos_concat_1" works OK - single tests the succeeds (and only tests the "true" case).
At changeset 3410:4a416d872806 (which fixed the boolean in the testing framework), testing "gpos_concat_1" works OK - with two tests, checking both "true" and "false" cases.
But changeset 3411:0c07212afc00 (which fixed the boolean bug not related to testing framework) broke the testing framework entirely: testing "gpos_concat_1" fails on both tests (together with all my tools which have a boolean parameter, even if those tests worked before).
-gordon _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
Hi Assaf, Sorry about all the back-and-forth on this, but I believe this is now fixed ( again ) in change set 3416:d995557d383b, which is now available in the distribution. On Feb 18, 2010, at 8:59 PM, Assaf Gordon wrote:
Hi,
I really appreciate your help with this, and I'm sorry to keep bothering you about the boolean thing, but:
It seems the recent successive changes to the boolean parameter are conflicting with one another (some changes made to the testing framework and others to the rest of galaxy).
At changeset 3402:bb50ac713feb (before the whole boolean issue start), testing "gpos_concat_1" works OK - single tests the succeeds (and only tests the "true" case).
At changeset 3410:4a416d872806 (which fixed the boolean in the testing framework), testing "gpos_concat_1" works OK - with two tests, checking both "true" and "false" cases.
But changeset 3411:0c07212afc00 (which fixed the boolean bug not related to testing framework) broke the testing framework entirely: testing "gpos_concat_1" fails on both tests (together with all my tools which have a boolean parameter, even if those tests worked before).
-gordon _______________________________________________ galaxy-dev mailing list galaxy-dev@lists.bx.psu.edu http://lists.bx.psu.edu/listinfo/galaxy-dev
Greg Von Kuster Galaxy Development Team greg@bx.psu.edu
participants (2)
-
Assaf Gordon
-
Greg Von Kuster