| Summary: | Patchtest migration from python2 to python3 | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Daniela Plascencia <daniela.plascencia> |
| Component: | Patchtest | Assignee: | Daniela Plascencia <daniela.plascencia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | bluelightning, leonardo.sandoval.gonzalez |
| Version: | 2.3 | ||
| Target Milestone: | 2.4 M3 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
| Bug Depends on: | |||
| Bug Blocks: | 10804 | ||
|
Description
Daniela Plascencia
2016-12-13 16:26:27 UTC
patchtest and the test suite are ready to be public and for the moment the main focus is on new tests and fixing possibles issues during 2.3 window. The migration is not urgent and patchtest can live with python 2.X at least for this release (2.3) Dany, I have pushed two branches called master-next on both projects: patchtest and patchtest-oe. These two contain most recent work including the migration except the meta-patchtest migration. This work needs to be concluded this Milestone (2.4M2) due to the importance and impact in the project. The framework migration is done, but the patchtest execution on "guest" is returning errors that must be solved before we can close this bug. Setting it to M3. master-next has the current implementation. Although not yet in master, this work is completed. |