[Toaster] Toaster Minutes 7/29/15
Jolley, Stephen K
stephen.k.jolley at intel.com
Wed Jul 29 08:57:00 PDT 2015
Attendees: Stephen, Sujith, Belen, Paul, Michael, Alex, Tiago, Victor, Brian, Mihail, Ed,
Updates:
Sujith: he will be working on a unit test for the importing layer functionality. Has been talking to Michael about that on the mailing list
Belén: documenting the design for the image customization feature
Paul: nothing Toaster related
Michael: project navigation changes and the project page change. Finished with that, and will be submitting a branch sometime this afternoon for review
Alex: bug fixing, working on the query sets for new Toaster tables, and improving unit tests
Tiago: spoke to branding team co-located with him to help with visual design, and working on redesigning the build dashboard page
Brian: nothing Toaster related
Mihail: working on fixing the back end test bugs. Presented to Brian last week on the Toaster testing plan, which should be sent to the mailing list by the end of the week.
Ed: 5 patches under review, 2 fixes for Bugzilla entries. Working on image customization related tasks: 8049 and 8075
Stephen - Working on YP and MinnowBoard project management.
Opens:
Michael - Mailing list patches on removing duplicated layers (is the same open as Ed's)
Ed: 8049 - We decided to create intermediate tables, but latest Alex patches suggest we no longer need them. Alex discussed the thinking and methods being used for the patches he has submitted. Brian will look at Alex's patch today and decide if we can live without the intermediate tables. Ed also points out that those intermediate tables will generate data duplication. Michael pointed out that those intermediate tables can be updated as required to reflect the latest status of a project, and they will diverge from the master data in the base tables. Paul also thinks the intermediates tables might improve performance. We still need a new table to list the packages added to a custom image (we cannot do without that one). This table should be very simple: just a list of packages to be added and deleted from an image recipe.
Alex: patch submission - Would like to understand when patch submission happens. Michael thinks whoever replies to the patch should take responsibility for submitting upstream. Alex asked if we should set a time frame for patch review: if nobody replies to his patches in say, 2 days, who should he ping? Brian suggested to ping people or the mailing list if you don't get responses.
Mihail - Testing. There are 4 test suites for Toaster.
1. OE-Selftest, which tests bb and oe-core. toaster.bbclass lives on oe-core which collects information coming from oe-core not bitbake. The quality of the info collected through that is tested with oe-selftest. Mihail can explain the tests and how to interpret the results.
2. django unit tests, which are very few still. Alex is working on adding new tests. They are regular django unit tests used with the test command from manage.py.
3. TTS contains the 3rd and 4th suites. The 3rd runs some smoke tests automatically for any patches sent for review to the Toaster mailing list. Alex will be adding to this too, things such as jshint and pylint tests to verify coding standards in patches.
4. The 4th suite contains the Selenium UI tests, which are intended to be integration tests.
Both TTS and Selenium tests you run them manually using bitbake/lib/toastercontrib/tts/runner.py (provides help before running tests). In tts/toasteruitests/run_toastertests.py is the same thing but provides no help before running the tests.
We should document all the above in the wiki (Alex and Mihail)
AR's:
Alex - Review the Toaster wiki page and identify was still useful and what's obsolete. (In process)
Alex - Document how to submit patches to bitbake-devel in the wiki, and how to send patches to prior releases. (Done)
Brian - Make a recommendation on Alex's patch today and decided if we need it in YP 1.9.
Mihail - Get access to Wiki and add QA tests to the wiki.
Alex - Add test information to the wiki
Thanks,
Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
* Work Telephone: (503) 712-0534
* Cell: (208) 244-4460
* Email: stephen.k.jolley at intel.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/toaster/attachments/20150729/0855e8f9/attachment.html>
More information about the toaster
mailing list