Parsing vs cached startup
I just ran a build from scratch and as expected, I got the full "Parsing recipes" for many minutes. I always start out with BB_NO_NETWORK=1 set so I can see what new files need to be downloaded (many of my customers are network limited and I like to provide them with the necessary files off-line). Sure enough, there was a new file this morning and my build stopped.
At this point I went to another machine and fetched the file
and put it into my download cache. I then restarted the build
on the original machine and I saw this:
Parsing recipes: 100% |#################################################################################| Time: 00:02:00 Parsing of 1262 .bb files complete (0 cached, 1262 parsed). 1689 targets, 87 skipped, 0 masked, 0 errors.
Why? Between the first aborted build and the retry, absolutely no recipes were changed. Only a single file was added to the source mirror.
What might have triggered this? Most of the time, I see the parse cache work as expected, but not always.
Are there any breadcrumbs left behind that might explain this?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------