meta-selftest: Add qemux86copy machine
PATCH 1/1 meta-selftest: Add qemux86copy machine
I know Martin finds something like this useful for testing sstate signatures, this adds one to meta-selftest so we can use it from oe-selftest in the sstate tests there too.
meta-selftest/conf/machine/qemux86copy.conf new file +3 -0
@@ -0,0 +1,3 @@ +require conf/machine/qemux86.conf + +MACHINEOVERRIDES .= ":qemux86"
Quoted 12 lines · Richard Purdie
I know Martin finds something like this useful for testing sstate signatures, this adds one to meta-selftest so we can use it from oe-selftest in the sstate tests there too.
Signed-off-by Richard Purdie <[email protected]>meta-selftest/conf/machine/qemux86copy.conf new file +0
-0
meta-selftest/conf/machine/qemux86copy.conf line 3
Quoted 3 lines
meta-selftest/conf/machine/qemux86copy.conf new file +3
-0@@ -0,0 +1,3 @@ +require conf/machine/qemux86.conf + +MACHINEOVERRIDES .= ":qemux86"
I wasn't changing MACHINEOVERRIDES (in case this would hide some possible sstate differences), instead I had to duplicate couple qemux86 overrides in linux-yocto, but this is still useful.
I'll drop my version after testing with sstate-diff-machines.sh that both return the same results.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 7 lines · Martin Jansa
Quoted 6 lines · Richard Purdie
I know Martin finds something like this useful for testing sstate signatures, this adds one to meta-selftest so we can use it from oe-selftest in the sstate tests there too.
Signed-off-by Richard Purdie <[email protected]>
Quoted 12 lines
meta-selftest/conf/machine/qemux86copy.conf line 3
Quoted 9 lines
meta-selftest/conf/machine/qemux86copy.conf new file +3
-0@@ -0,0 +1,3 @@ +require conf/machine/qemux86.conf + +MACHINEOVERRIDES .= ":qemux86"I wasn't changing MACHINEOVERRIDES (in case this would hide some possible sstate differences),
I think this actually makes it more likely to highlight differences, but either way, the tests I ran did highlight a raft of issues and it seems to be good enough to find several problems. I've sent enough fixes to make the new selftest pass.
Quoted 5 lines
instead I had to duplicate couple qemux86
overrides in linux-yocto, but this is still useful.I'll drop my version after testing with
sstate-diff-machines.shthat both return the same results.
Sounds good.
FWIW you can run the new test with:
oe-selftest --run-tests sstatetests.SStateTests.test_sstate_sametune_samesigs
in case that isn't clear. It doesn't rely on building anything so is comparatively fast.
Cheers,
Richard
Quoted 32 lines · Richard Purdie
Quoted 7 lines · Martin Jansa
Quoted 6 lines · Richard Purdie
I know Martin finds something like this useful for testing sstate signatures, this adds one to meta-selftest so we can use it from oe-selftest in the sstate tests there too.
Signed-off-by Richard Purdie <[email protected]>Quoted 12 lines
meta-selftest/conf/machine/qemux86copy.conf line 3
Quoted 9 lines
meta-selftest/conf/machine/qemux86copy.conf new file +3
-0@@ -0,0 +1,3 @@ +require conf/machine/qemux86.conf + +MACHINEOVERRIDES .= ":qemux86"I wasn't changing MACHINEOVERRIDES (in case this would hide some possible sstate differences),
I think this actually makes it more likely to highlight differences, but either way, the tests I ran did highlight a raft of issues and it seems to be good enough to find several problems. I've sent enough fixes to make the new selftest pass.
Quoted 5 lines
instead I had to duplicate couple qemux86
overrides in linux-yocto, but this is still useful.I'll drop my version after testing with
sstate-diff-machines.shthat both return the same results.
Quoted 8 lines
Sounds good.
FWIW you can run the new test with:
oe-selftest --run-tests sstatetests.SStateTests.test_sstate_sametune_samesigs
in case that isn't clear. It doesn't rely on building anything so is comparatively fast.
same as ssstate-diff-machines.sh --analyze :)
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]