I would like to use the read-only hashserv with a dunfell build. To test, I
created one based on kirkstone and built the dunfell image using that
hashserv creating a new sstate-cache.
Then, I created a read-only hashserv which used the database of that first
hashserv instance. I started a new build which used the read-only hashserv
and sstate-cache as a PREMIRROR. It required a rebuild of several packages,
and the build printed out warnings like the following:
WARNING: initscripts-1.0-r155 do_populate_lic: Error contacting Hash
Equivalence Server 127.0.0.1:18686: Connection closed
WARNING: initscripts-1.0-r155 do_deploy_source_date_epoch: Error contacting
Hash Equivalence Server 127.0.0.1:18686: Connection closed
The read-only hashserv reports messages like the following:
Unrecognized command {'report': {'taskhash':
'4c79c264282b9bbe444bf9da101e889187a38287711ad09995279b10d19a52a1',
'method': 'oe.sstatesig.OEOuthashBasic', 'outhash':
'be486a087ff983999e0db3e5b4d8b1657b4c849d44202a2abf5d32e9a6ade11a',
'unihash':
'4c79c264282b9bbe444bf9da101e889187a38287711ad09995279b10d19a52a1'}}
Is this how I should do it? After reviewing the hashserv code, I think my
dunfell hashserv client might not handle a read-only hashserver properly,
so it prints those warnings. Do you agree?
Thanks,
Jate S.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168610):
https://lists.openembedded.org/g/openembedded-core/message/168610
Mute This Topic: https://lists.openembedded.org/mt/92673675/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
