[utah-devel] UTAH Weekly meeting notes
Here are the notes for this weeks UTAH meeting. Javier - working on ISO, raring currently freezes, Siva has a bug open Joe - working on utah - dashboard improvements. - changing client to output only yaml so the utah server can more easily parse it. Max - add config directory support and for publish results -- Ubuntu-utah-devel mailing list Ubuntu-utah-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-utah-devel
[utah-devel] UTAH Weekly Meeting
Attendees: Gema Gomez-Solano Javier Collado James Page Joe Talbott Max Brustkern Notes: Max - working on training material - working on fixing bugs in jenkins - will merge into stable (i.e. trunk) branch Joe - updated 'fetch_cmd' to 'fetch_method' and 'fetch_location' - will walk through training material and update for latest changes. Javier - updated package installation method. - merge proposal handling. - fix duplicated questions in preseeds - allow empty ts_control file - testcase migration - postponed to fix UTAH issues on Quantal Gema - Need to have UTAH working on Quantal for UDS James - no updates Bug Report: To follow. -- Ubuntu-utah-devel mailing list Ubuntu-utah-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-utah-devel
[utah-devel] Attention - fetch_cmd has changed in the dev branch
Hi All, If you're using lp:utah or the daily ppa please note. In your master.run files 'fetch_cmd' has been deprecated in favor of 'fetch_method' and 'fetch_location'. This allows us better control of the testsuite fetch process and tracability, as we can now determine the revision of the testsuite being used. fetch_method - One of 'bzr', 'bzr-export', or 'git' 'bzr' does a 'bzr branch fetch_location'. 'bzr-export' does a 'bzr export fetch_location'. 'git' does a 'git clone fetch_location'. fetch_location - Should be a valid repository location for the supplied fetch_method. Either remote or local repositories should work. One caveat to note is that bzr-export requires getting the revision information from the repository versus the working tree and thus introduces a small race where an update can happen between pulling the repo and checking the revision. This work is in utah/client/common.py and has been designed to make adding new version control systems as easy as possible. Thanks, Joe -- Ubuntu-utah-devel mailing list Ubuntu-utah-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-utah-devel
[utah-devel] tslist.run confusion
Hi all, Max opened a bug this morning that brought up a point of confusion regarding the tslist.run file. We accept 'command' at the top-level of a test entry. I.e. - test: blah command: echo blah But we also accept 'overrides' which can contain anything a tc_control file can contain including command. I.e. - test: blah overrides: timeout: 10 command: echo overridden blah tc_setup: echo overridden tc_setup ... This is confusing. I see two options. 1. don't allow 'command' at the top-level of a test entry. pros: 1. easy to implement 2. removes a bit of the confusion cons: 1. 'overrides' is redundant and I think ideally we'd allow any tc_control option at the top-level of a test entry 2. move 'overrides' entries to top-level pros: 1. simplifies file structure for testsuite/case authors 2. even less confusing cons: 1. more difficult to implement since we need to basically use the tc_control file schema plus the test entry. 2. having a section named 'overrides' clearly shows that the entries override something (hopefully it's obvious that tc_control entries are being overridden). Thoughts? Thanks, Joe -- Ubuntu-utah-devel mailing list Ubuntu-utah-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-utah-devel
