linux/poky.git/bitbake/bin/bitbake-hashclient, branch 5.2_M2Mirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=5.2_M22024-10-25T14:40:03+00:00bitbake: bitbake-hashclient: Add help for address2024-10-25T14:40:03+00:00Joshua WattJPEWhacker@gmail.com2024-10-15T16:00:18+00:00urn:sha1:b5f17d0334532a475eb05f6dc7e7e39187d2573e
Adds an epilog to the help text that indicates the possible options for
the server address
(Bitbake rev: b6b703fce02057212ad11b1d1286c6178c533bad)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-hashclient: Improve ping command line options2024-05-28T22:46:21+00:00Joshua WattJPEWhacker@gmail.com2024-05-23T16:44:54+00:00urn:sha1:e598b2d135712d79577ac8ec95fc89735571687f
Adds a --quiet option to suppress the message for each ping, and report
the median ping time.
(Bitbake rev: 3c85b5e2d9b9c39507ed362aaa115b7f6f155966)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-hashclient: Improve stress statistics reporting2024-05-23T10:27:08+00:00Joshua WattJPEWhacker@gmail.com2024-05-22T17:12:20+00:00urn:sha1:5f602c1bd57e1623ba2d46d374782e27c9547af3
Improves the way statistics are reported for the stress test. This makes
it easier to compare them to the ping test
(Bitbake rev: ce166ae25793c11b0a190c531bef0c296fd74497)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-hashclient: Add ping command2024-05-23T10:27:08+00:00Joshua WattJPEWhacker@gmail.com2024-05-22T16:29:43+00:00urn:sha1:76421d5742ecca6344f3035378f89c2fc3a5ae05
Adds a ping subcommand to bitbake-hashclient which can be useful to
measure connection latency
(Bitbake rev: 337487fdffae92091fc33b2346d46c39db5a130f)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-hashclient: Warn on bad .netrc2024-03-26T17:11:15+00:00Joshua WattJPEWhacker@gmail.com2024-03-25T15:56:32+00:00urn:sha1:f2ff622a4c83948f7612c535034f5dbcb28781a8
If there is an error parsing .netrc, warn the user on stderr
(Bitbake rev: 6366ea8d9c284d10bb8f4129004b55239d9022c0)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: hashserv: Add unihash-exists API2024-02-19T11:58:12+00:00Joshua WattJPEWhacker@gmail.com2024-02-18T22:59:48+00:00urn:sha1:3bd2c69e70853584beaaa5a4fd62589fa051d911
Adds API to check if the server is aware of the existence of a given
unihash. This can be used as an optimization for sstate where a client
can query the hash equivalence server to check if a unihash exists
before querying the sstate cache. If the hash server isn't aware of the
existence of a unihash, then there is very likely not a matching sstate
object, so this should be able to significantly cut down on the number
of negative hits on the sstate cache.
(Bitbake rev: cfe0ac071cfb998e4a1dd263f8860b140843361a)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: hashserv: Add Unihash Garbage Collection2024-02-19T11:58:12+00:00Joshua WattJPEWhacker@gmail.com2024-02-18T22:59:46+00:00urn:sha1:1effd1014d9140905093efe25eeefedb28a10875
Adds support for removing unused unihashes from the database. This is
done using a "mark and sweep" style of garbage collection where a
collection is started by marking which unihashes should be kept in the
database, then performing a sweep to remove any unmarked hashes.
(Bitbake rev: 433d4a075a1acfbd2a2913061739353a84bb01ed)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-hashclient: Add commands to get hashes2023-12-02T18:04:23+00:00Joshua WattJPEWhacker@gmail.com2023-11-30T17:03:43+00:00urn:sha1:6b6374c336016ee56ff7418c45d1eba2eac95b21
Adds subcommands to query the server for equivalent hashes and for
output hashes.
(Bitbake rev: 36ba202232399738670c9fb11169ead5590a3e82)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: bitbake-hashclient: Output stats in JSON format2023-11-09T17:33:03+00:00Joshua WattJPEWhacker@gmail.com2023-11-03T14:26:36+00:00urn:sha1:a607f435de1a04fed655a0f25d5a74724ba82ce0
Outputting the stats in JSON format makes more sense as it's easier for
a downstream tool to parse if desired.
(Bitbake rev: 3a18066e479ab06bdb08e258fc4aacad5e73222e)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: hashserv: Add database column query API2023-11-09T17:33:03+00:00Joshua WattJPEWhacker@gmail.com2023-11-03T14:26:34+00:00urn:sha1:c1574ae46f7a5701d79f2c1d333094a5d5919a46
Adds an API to retrieve the columns that can be queried on from the
database backend. This prevents front end applications from needing to
hardcode the query columns
(Bitbake rev: abfce2b68bdab02ea2e9a63fbb3b9e270428a0a6)
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>