Note about running functional tests.
Dear Galaxy admins, As of 10408:6822f41bc9bb stable/10409:2ca0b65d5005 default, a bug has been fixed where running functional tests could overwrite some files in your Galaxy path. If you intend to run functional tests, it is recommended to update to the relevant revision on the branch you are running. Additionally, it is not recommended to run functional tests on a production instance, since the test suite alters a number of configuration settings on the fly, with the result being that it is not a reliable test of the exact production environment, which may give misleading results. -- --Dave B.
On Mon, Aug 19, 2013 at 6:25 PM, Dave Bouvier <dave@bx.psu.edu> wrote:
Dear Galaxy admins,
As of 10408:6822f41bc9bb stable/10409:2ca0b65d5005 default, a bug has been fixed where running functional tests could overwrite some files in your Galaxy path. If you intend to run functional tests, it is recommended to update to the relevant revision on the branch you are running.
Nasty - thanks for the warning.
Additionally, it is not recommended to run functional tests on a production instance, since the test suite alters a number of configuration settings on the fly, with the result being that it is not a reliable test of the exact production environment, which may give misleading results.
Hang on - is that a short term warning? We *want* to run the functional tests on our production Galaxy precisely to check the tools are installed and working there. Thanks, Peter
On Mon, Aug 19, 2013 at 6:35 PM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
On Mon, Aug 19, 2013 at 6:25 PM, Dave Bouvier <dave@bx.psu.edu> wrote:
Dear Galaxy admins,
As of 10408:6822f41bc9bb stable/10409:2ca0b65d5005 default, a bug has been fixed where running functional tests could overwrite some files in your Galaxy path. If you intend to run functional tests, it is recommended to update to the relevant revision on the branch you are running.
Nasty - thanks for the warning.
I can see this on galaxy-dist (the development repository), but when will this be available on galaxy-central? https://bitbucket.org/galaxy/galaxy-dist/commits/all/ Peter
Peter, The fix is now available in both galaxy-dist and galaxy-central. --Dave B. On 8/19/13 13:39:29.000, Peter Cock wrote:
On Mon, Aug 19, 2013 at 6:35 PM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
On Mon, Aug 19, 2013 at 6:25 PM, Dave Bouvier <dave@bx.psu.edu> wrote:
Dear Galaxy admins,
As of 10408:6822f41bc9bb stable/10409:2ca0b65d5005 default, a bug has been fixed where running functional tests could overwrite some files in your Galaxy path. If you intend to run functional tests, it is recommended to update to the relevant revision on the branch you are running.
Nasty - thanks for the warning.
I can see this on galaxy-dist (the development repository), but when will this be available on galaxy-central? https://bitbucket.org/galaxy/galaxy-dist/commits/all/
Peter
On Mon, Aug 19, 2013 at 1:35 PM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Additionally, it is not recommended to run functional tests on a production instance, since the test suite alters a number of configuration settings on the fly, with the result being that it is not a reliable test of the exact production environment, which may give misleading results.
Hang on - is that a short term warning? We *want* to run the functional tests on our production Galaxy precisely to check the tools are installed and working there.
How are you doing this currently? I can understand running the tests in your production Galaxy environment, but they should always be run with a separate database and files directory.
On Mon, Aug 19, 2013 at 7:09 PM, James Taylor <james@jamestaylor.org> wrote:
On Mon, Aug 19, 2013 at 1:35 PM, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Additionally, it is not recommended to run functional tests on a production instance, since the test suite alters a number of configuration settings on the fly, with the result being that it is not a reliable test of the exact production environment, which may give misleading results.
Hang on - is that a short term warning? We *want* to run the functional tests on our production Galaxy precisely to check the tools are installed and working there.
How are you doing this currently? I can understand running the tests in your production Galaxy environment, but they should always be run with a separate database and files directory.
Exactly, using run_functional_tests.sh should be creating a temporary one off database (without touching or even reading the main database), and only using temporary directories for its files (without touching the real user data on disk). Apart from this recent bug, that has been working, right? There's a separate issue about which *.loc files to use, I would like *.loc.sample to be used during testing: http://lists.bx.psu.edu/pipermail/galaxy-dev/2013-April/014370.html Regards, Peter
participants (3)
-
Dave Bouvier
-
James Taylor
-
Peter Cock