Skip to content

auto.conf: Configure BB_HASHSERVE_DB_DIR to use the shared SSTATE_DIR - #369

Merged
rajendra-desai-ni merged 1 commit into
ni:nilrt/master/nextfrom
Shreejit-03:AzDo_BB_Hashserve_DB_DIR_warning
Aug 3, 2026
Merged

auto.conf: Configure BB_HASHSERVE_DB_DIR to use the shared SSTATE_DIR#369
rajendra-desai-ni merged 1 commit into
ni:nilrt/master/nextfrom
Shreejit-03:AzDo_BB_Hashserve_DB_DIR_warning

Conversation

@Shreejit-03

@Shreejit-03 Shreejit-03 commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Changes

The sstate cache is shared across multiple build directories, while the hash equivalence database was previously created inside each individual build directory. This prevented builds from sharing hash equivalence information, reducing sstate reuse and generating warnings during the build.

Store the hash equivalence database alongside the shared sstate cache so all builds use the same database, improving sstate reuse and resolving the warning about the hash equivalency database location.

Justification

AB#3918195.

Testing

Followed similar steps as done here and verified the changes.

Suggested Reviewers:

  • @ni/rtos

@Shreejit-03
Shreejit-03 requested a review from a team as a code owner July 27, 2026 23:23
@chaitu236
chaitu236 requested a review from Copilot July 28, 2026 21:54

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Azure DevOps Yocto/BitBake auto-configuration so the hash equivalence database is stored in the shared sstate cache location, enabling hash equivalence reuse across multiple build directories and avoiding warnings about per-build DB placement.

Changes:

  • Set BB_HASHSERVE_DB_DIR to ${SSTATE_DIR} so all builds sharing the same sstate cache also share the hash equivalence database.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@chaitu236 chaitu236 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sstate cache is shared across multiple build directories, while the
hash equivalence database was previously created inside each individual
build directory.

This wording is very confusing; what is meant by "multiple build directories" and "each individual build directory"? We only have one build directory right?

Store the hash equivalence database in SSTATE_DIR instead of the
per-build workspace.

The build workspace is recreated for each pipeline run, while the
sstate cache persists across builds. Storing the database alongside
the sstate cache allows hash equivalence information to persist across
builds, improving sstate reuse and resolving the warning about the
database location.

Signed-off-by: Shreejit C <shreejit.c@emerson.com>
@Shreejit-03
Shreejit-03 force-pushed the AzDo_BB_Hashserve_DB_DIR_warning branch from a5d1e2a to da7fe4b Compare July 29, 2026 20:11
@Shreejit-03
Shreejit-03 requested a review from chaitu236 July 29, 2026 20:11
@rajendra-desai-ni
rajendra-desai-ni merged commit b11f8c7 into ni:nilrt/master/next Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants