| Message ID | 20250408165842.2014509-1-skandigraun@gmail.com |
|---|---|
| State | Accepted, archived |
| Commit | 64175a41f48fce69a5205000865cc3b8648476f7 |
| Headers | show |
| Series | yocto-check-layer: expect success for test_patches_upstream_status | expand |
diff --git a/scripts/lib/checklayer/cases/common.py b/scripts/lib/checklayer/cases/common.py index 51233de767..ddead69a7b 100644 --- a/scripts/lib/checklayer/cases/common.py +++ b/scripts/lib/checklayer/cases/common.py @@ -104,7 +104,6 @@ class CommonCheckLayer(OECheckLayerTestCase): self.tc.layer['name']) self.fail('\n'.join(msg)) - @unittest.expectedFailure def test_patches_upstream_status(self): import sys sys.path.append(os.path.join(sys.path[0], '../../../../meta/lib/'))
When the Upstream-Status tag for patches became mandatory, the test verifying the presence of this tag was made to not fail the layer compatibility tests, in order to allow time for the maintainers to adapt to this change. This was two years before this commit. Since then the layer compatibility script shows a cryptic "unexpected success" result for this test, which of course becomes clear once one checks the code and commit history, but it is a nuisance still, which shouldn't be needed to understand the result. This commit removes the the related annotation so the compatibility check will pass or fail with a clear message - in hope that 2 years was enough for active maintainers to adjust their patches. Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> --- scripts/lib/checklayer/cases/common.py | 1 - 1 file changed, 1 deletion(-)