| Summary: | Upstream-Status Submitted and Inappropriate check for where/reason info | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez> |
| Component: | Patchtest | Assignee: | Daniela Plascencia <daniela.plascencia> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | bluelightning |
| Version: | 2.4 | ||
| Target Milestone: | 2.5 M1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Leonardo Sandoval Gonzalez
2017-05-17 14:38:50 UTC
Moving to M4 waiting for an execution issue to be solved (bitbake/tinfoil related). Should this check be inside the format unit test or be set as a separate one? (In reply to comment #2) > Should this check be inside the format unit test or be set as a separate one? inside. This should be part of test_patch_upstream_status.test_upstream_status_format Moving to 2.5 M1, I'll work on all enhancements on such milestone. |