| Summary: | Include automated test execution and reporting in Autobuilder | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Benjamin Esquivel <benjamin.esquivel> |
| Component: | autobuilder | Assignee: | Aaron Chan <aaron.chun.yew.chan> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | aaron.chun.yew.chan, apoorv.sangal, bill.randle, bluelightning, ee.peng.yeoh, infras.ab.watcher, Infras.watcher, joshuagloe, leonardo.sandoval.gonzalez, richard.purdie, ross.burton |
| Version: | 2.2 | ||
| Target Milestone: | 4.99 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| URL: | http://centaurus01.png.intel.com:8010/builders/nightly-testopia/builds/60 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Benjamin Esquivel
2016-05-26 20:11:55 UTC
My fault, moving it to M1 again. CCB should agree on any milestone movement. Demo created (http://git.yoctoproject.org/cgit/cgit.cgi/qa-tools/) but it needs more work in order to close this bug. This becomes a High if moved to 2.2 M3 This work wont be ready for this release. Moving to next release, expecting more involvement from QA team. Anibal, can you please comment on this one. Ideas to split it? (In reply to comment #5) > Anibal, can you please comment on this one. Ideas to split it? There are two needed tasks for complete this, 1) Finish the testopia_update script. 2) Add the buildstep into the Autobuilder for automatic report (call testopia_update). Currently Jose Perez done the 1) part so the only remaining part will be add the buildstep. I'll change the owner to Jose Perez and now the split isn't needed. *** Bug 10580 has been marked as a duplicate of this bug. *** With reference to http://git.yoctoproject.org/cgit/cgit.cgi/qa-tools/ Base on the usage model of the testopia_update.py script, it appears that the test cases update is much faster manually compare to updating the test cases result using the script sourcing with the results logfiles. In some cases, the results updating results into Testopia appeas to be locking up, unresponsive for several hours and unable to fully complete the result publishing even when running on a bare-metal server. Hence the testopia_update.py script require some effort to debug and analysis the issue am facing. On other areas of enhancement which was tested in autobuilder. 1. Added a patch UploadTestopia.py as an automated buildstep option 2. Modify the buildset-config jobs to adopt the buildstep in item 1. 3. Changes to the job specific interface to accept "Test Run ID" as string parameter to invoke the testopia_update script to upload the auto testcases Issue Blocking: 1. Testopia_update.py script does not work as per expected 2. Logfiles can be generated in various paths, different logfile names, and some job configuration requires multiple logfiles of various test shares the same test run ID in Testopia. This ticket is back dated 2 years ago and the direction has been moved to test cases management to a different platform whereby Testopia will be retired replacing by other Test case management tool by the community. Hence, this ticket is no longer valid and the status is now changed to Never Fix. A new ticket should be raised indicating the same motivation and assign to the dedicated owner currently working on the enhancements. |