Bug 10194 - bitbake-whatchanged is broken
Summary: bitbake-whatchanged is broken
Status: RESOLVED OBSOLETE
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: Scripts and Tools (show other bugs)
Version: 2.3
Hardware: x86 Multiple
: Medium normal
Target Milestone: 5.99
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on: 10193
Blocks:
  Show dependency tree
 
Reported: 2016-08-30 08:57 UTC by Robert Yang
Modified: 2025-10-23 15:09 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Yang 2016-08-30 08:57:19 UTC
It uses "STAMPS_DIR=/another/dir bitbake -S none <recipe>" to generate new stamps and compare to old stamps to get the data, but now once STAMPS_DIR is changed, the old stamps and work dir will be removed, so that it doesn't work any more.

We may look for other ways to fix it in YP 2.3, for example, add handler or use the handler printdiff for -S to fix the problem.

And comments from RP:
I don't believe that script always worked as it should and I really want to see usecases and better tests of what its showing rather than just blindly reimplmenting it in runqueue.py
Comment 1 Randy MacLeod 2020-04-23 07:51:07 UTC
delete bitbake-whatchanged since it has been broken for years.
Comment 2 Randy MacLeod 2022-05-05 15:20:35 UTC
WE'll check and perhaps remove the script.
Comment 3 Randy MacLeod 2023-10-24 14:24:50 UTC
Bulk move from 4.99 or 0.00 to 5.99
Comment 4 Ross Burton 2025-10-23 15:08:43 UTC
Removed from f8193978eb0944e693e6a5cfbf9035e104e489f0.