Repository navigation
evetest: use adam 0.0.85 - #6798
Merged
Merged
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pins evetest to Adam 0.0.85, the release that carries lf-edge/adam#163: Adam built against the eve-api revision that merged lf-edge/eve-api#155 (CPU placement).
Adam stores device info re-encoded with its own copy of the API, so without this the CPU placement fields (
ZInfoDevice.cpu_pools,ZInfoApp.cpu_placement_status/cpu_placement_error/assigned_cpus, the CPU topology in the hardware inventory,optional_capabilities.cpu_placement) never reach a test. The CPU placement tests in #6335 depend on it.Same three places as the 0.0.82 update:
Dockerfile.evetest,Makefile,constants/config.go.lfedge/adam:0.0.85has the same digest as the image of #163's merge commit.