Its been a few weeks since I sent one of these out, mainly as I've not had much to report.
Pending Patches =============== Patches have been steadily getting reviewed and merged. Some things took a little longer than is ideal due to travel on Saul and my part. I know Saul is still travelling. Autobuilder status is much improved compared to where its been the past couple of weeks. We added a number of new sanity tests, they found issues, we've now got many of them fixed. The nightly-qa test is still problematic, the fsl-ppc machines are continuing to fail and have been failing for a while now :(. Automated QA ============ Architecture/planning wise, there is a big shakeup of the automated QA tests coming down the pipeline for 1.5. The current shell script based system isn't scaling so we're looking at moving to python unittest. Why is this important? Manual QA currently uses a lot of or QA resources and means releases take longer than we'd like, we also have issues if we ever try two in parallel (e.g. a point release). I want to see this problem removed and automation looks like the best way to achieve it. It means the QA teams can then focus on more automation and writing new test cases for new features and so on. Once the initial conversion happens, we're looking to convert many of the currently manual tests over to become automated and hence improve the speed we can put releases through the QA process amongst other things. This is all still being planned, further discussion will no doubt happen as soon as there is a plan to propose/discuss. There are a variety of open bugs in the bugzilla and people interested in what is going on can look at those and see the rough plans for 1.5. I can quickly summarise that: a) this work is focused on testing with qemu, not target hardware. Nothing done in this work would be incompatible with real hardware, its just not a focus right now (maybe 1.6?) b) We plan to leverage existing tests where we can, e.g. "make check" on target using ptest packages c) initially the plan is to cover the runtime qemu tests d) we're also looking at some kind of oe-selftest, a bit like bitbake-selftest which would run "bitbake X, change Y, bitbake X, check something" type scenarios. e) extensions to the package QA tests (insane.bbclass) are being considered f) a new level of QA tests against rootfs after they're generated will likely be created The plan is to establish the new python unittest code using a small team, then open things up for more contributions of test cases since this part of the process can be parallelised. 1.3.2 ===== It shipped! Thanks Ross! :) Hopefully this should round out the bulk of the 1.3 issues people were running into. There is no 1.3.3 planned at this point. 1.4.1 ===== A number of fixes were merged for this. I know there are a small number of patches still to come in but we'll need to start putting this through the release process shortly so please get any requests for bugs fixes for 1.4.x to Paul ASAP. Bitbake ======= I've been spending quite a bit of time reviewing and also writing some changes to the core of bitbake, splitting up cooker. These changes set the scene for webhob and the memory resident bitbake concept as well as removal of the double bitbake execution. There will be more changes in this area landing and there may be some further mild instability whilst we work though any issues. There have also been some patches which remove the "global method scope" we had in bitbake. Those patches merged, I've not heard of anyone with issues due to them yet (the parallel parsing already half broke the global scope anyway). Cheers, Richard _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto