Bug 13757 - run-ptest not listed in sources
Summary: run-ptest not listed in sources
Status: RESOLVED FIXED
Alias: None
Product: Layer Index
Classification: Yocto Project Subprojects
Component: Layer Index (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 6.99
Assignee: Unassigned
QA Contact: apoorv sangal
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-01-27 14:28 UTC by Tuomas Salokanto
Modified: 2026-08-10 01:22 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tuomas Salokanto 2020-01-27 14:28:23 UTC 
Layer Index does not list run-ptest file in the sources for packages that have ptest enabled. It could be listed there for easy access like other oe-specific files that are not in upstream.
Comment 1 Richard Purdie 2020-01-28 11:20:26 UTC 
I suspect this is because the layerindex parses nodistro config and ptest isn't enabled with the defaults in nodistro. The file therefore isn't there in the configuration the layerindex parses/sees. Not sure how we'd fix that other than changing the defaults for nodistro.
Comment 2 Ross Burton 2020-01-30 15:52:39 UTC 
Richard's theory is sadly incorrect. Concrete example is Pango:

http://layers.openembedded.org/layerindex/recipe/488/

The layer index says there's a single source (the tarball) and a single patch. But the recipe says:

SRC_URI += "file://run-ptest \
            file://0001-Fix-build-reproducibility.patch"

My hunch is that the layer index is taking the list of all SRC_URI entries, counting remote files as sources and patch files as patches.  run-ptest is neither, so doesn't get listed.
Comment 3 akuster 2021-04-22 15:29:13 UTC 
this issue is not limited to run-ptest. Any files that are local are not shown.
Comment 4 Randy MacLeod 2022-05-12 15:20:22 UTC 
Ross to provide details on demand!
Comment 5 Tim Orling 2022-10-24 22:41:09 UTC 
Not likely to get to this anytime soon. Moving to "Unassigned".
Comment 6 Randy MacLeod 2023-10-30 15:37:33 UTC 
Build move to 5.0 -- ../Randy
Comment 7 Randy MacLeod 2024-04-25 01:13:54 UTC 
Bulk move of 5.0 medium importance issues to 5.99.
Move to 5.1 if you want to actively work on an issue.
Comment 8 Randy MacLeod 2024-04-25 01:23:11 UTC 
Move to 5.99 since no one is actively working on this issue.
Move to 5.x if you start on a task, please.
Comment 9 Tim Orling 2026-06-25 17:02:00 UTC 
Still valid. Bumping to 6.99.