Op 06-04-2022 om 23:05 schreef Richard Purdie:
On Wed, 2022-04-06 at 21:44 +0200, Ferry Toth wrote:
Hi
Op 06-04-2022 om 17:23 schreef Richard Purdie:
On Wed, 2022-04-06 at 16:43 +0200, Ferry Toth wrote:
Op 06-04-2022 om 13:40 schreef Richard Purdie:
On Tue, 2022-04-05 at 17:23 +0200, Ferry Toth wrote:
Op 04-04-2022 om 22:39 schreef Richard Purdie:
On Mon, 2022-04-04 at 19:35 +0200, Ferry Toth wrote:
Op 04-04-2022 om 15:58 schreef Richard Purdie:
On Sun, 2022-04-03 at 21:50 +0200, Ferry Toth wrote:
Looking at the patches I wondered if this would break testimage and
unfortunately it does:
https://autobuilder.yoctoproject.org/typhoon/#/builders/50/builds/50
13/s
teps/12/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/76/builds/49
75
That is weird, do I understand correctly that it fails on:
apt-get remove --yes run-postinsts-dev
Reading package lists...
Building dependency tree...
E: Unable to locate package run-postinsts-dev
That is actually *) one line I didn't touch. I did note while testing
that I saw this exact message, however that was not counted as a fail.
What could cause this? Because the complaint is it can't remove the
package because it was not installed.
It would be trivial to remove the line
*) self.pkg('remove --yes run-postinsts-dev')
but how could it have passed the test before?
I think the issue is you edited testimage which is a different set of
tests
which aren't just called by oe-selftest but by things like
That would be my first thought too, but...
because the failure seems to be on the line self.pkg('remove --yes run-
postinsts-dev'), that would mean the line self.pkg('update') passed.
And that should only pass if it finds a signed repository and has the key
installed (and believe me, I saw a log of that in the last week).
So, there may be a second thing wrong?
I was easily able to reproduce this locally and it shows the
setup_source_config_for_package_install() step fails and hence the sources
aren't setup correctly, hence the update probably works.
not correct, hence works. You lost me here, but I'll try to reproduce.
I mean the command doesn't work correctly. In my local logs I see:
DEBUG: Command: cd /etc/apt/; cp sources.list sources.list.bak; sed -i
's/\[trusted=yes\] http:\/\/bogus_ip:bogus_port/http:\/\/192.168.7.1:46599/g'
sources.list
Status: 1 Output: cp: can't stat 'sources.list': No such file or directory
sed: sources.list: No such file or directory
go in and find/share them. The issue does locally reproduce for me with a
"bitbake core-image-sato -c testimage" with package_deb set as the backend.
..in conf. But without PACKAGE_CLASSES, PACKAGE_FEED_GPG_NAME,
PACKAGE_FEED_GPG_PASSPHRASE_FILE?
Yes.
Yes, regardless the above, we need to either make signing always enabled
in
all test cases or detect whether signing is used.
Do you have a hint if there is a variable to test in class AptRepoTest if
PACKAGE_FEED_GPG_NAME has been set?
Otherwise I could just duplicate code and create
apt.AptRepoTest.test_apt_install_from_repo_signed.
What would you prefer?
We should be able to test self.tc.td.get('PACKAGE_FEED_GPG_NAME') in the
test
and handle accordingly?
I'll try this for autodetecting the test case.
I did merge the base changes into the release since I thought it was fair to
get
the fixes in before it was built. We just need to get the test sorted now, I
think it is close.
Thanks for merging.
I'll fix the test, that's only fair.
One thing, the test "test_testimage_apt" is new. It needs to be scheduled
somewhere (where "test_testimage_dnf" is called i guess), I didn't add that.
Is that correct?
No, the autobuilder runs all the tests in oe-selftest so it should be covered
(and is why we saw the failures on the autobuilder).
I was running 'oe-selftest -K -r
runtime_test.TestImage.test_testimage_apt' whereas buildbot seems to be
running 'apt.AptRepoTest.test_apt_install_from_repo' directly.
We have several types of test. There are two types in play here,
"oe-selftest -K -r runtime_test.TestImage.test_testimage_apt"
and
"bitbake core-image-sato -c testimage"
Thanks for the explanation. Yesterday evening I built Sato and was able
to reproduce the issue.
(that was a big build with half of build time spent on building Rust).
core-image-sato does not have a /etc/apt/sources.list, the selftest public key
is not on the image and gpg is not installed. This explains the errors in the
log.
The latter testimage tests are often run every time we create images and running
testimage will trigger 'apt.AptRepoTest.test_apt_install_from_repo' if the image
has apt present and is built using debian package management.
We also run oe-selftest which triggers a testimage of it's own for a specfic
test case.
Got it.
So we'd expect the normal testimage calls to not have the package signing
enabled and then we'd have the oe-selftest which specifically tests signing.
However, test_testimage_apt is where keys are setup (keys found in
meta-selftest). So, where/when is test_testimage_apt called (or
test_testimage_dnf for that matter)?
Those are called by the oe-selftest call on the autobuilder. We run the oe-
selftest with a mask on the autobuilder so pretty much all of them run.
After looking at more detail at autobuilder schedules I get it.
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#164104):
https://lists.openembedded.org/g/openembedded-core/message/164104
Mute This Topic: https://lists.openembedded.org/mt/90226708/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
