Skip to content

ci: test_entrypoint: drop the kmods feed before installing packages - #130

Draft
BKPepe wants to merge 1 commit into
openwrt:mainfrom
BKPepe:tolerate-stale-kmods-feed
Draft

ci: test_entrypoint: drop the kmods feed before installing packages#130
BKPepe wants to merge 1 commit into
openwrt:mainfrom
BKPepe:tolerate-stale-kmods-feed

Conversation

@BKPepe

@BKPepe BKPepe commented Aug 13, 2026

Copy link
Copy Markdown
Member

The runtime-test containers are built from the openwrt/rootfs:<arch>-<branch> images, which carry the kmods feed URL for the exact kernel they were built with. When the branch moves to a newer kernel, the old kmods directory is removed from the download server and opkg update inside the container fails with a 404, so every runtime test fails even though the tested package built fine. This is currently the case for all -openwrt-24.10 images (see e.g. openwrt/packages#30260, where the package compiles on all architectures but the runtime tests fail with a 404 on the kmods feed).

The tests install the built packages from the local packages_ci feed and do not need the kmods feed, so drop it from the feed configuration before updating. The apk-based branches generate the same kmods entry in distfeeds.list (include/feeds.mk in openwrt.git), so both package managers get the same treatment.

This complements openwrt/docker#208, which keeps the images fresh — this change keeps the tests working when they are not.

The kmods feed only exists for the exact kernel the rootfs image was
built with. Once the branch moves to a newer kernel, the old kmods
directory is removed from the download server and opkg update inside
the container fails with a 404, taking down every runtime test even
though the tested package built fine. The tests install the built
packages from the local packages_ci feed and do not need the kmods
feed, so drop it from the feed configuration instead of failing on it.

The apk-based branches generate the same kmods entry in
distfeeds.list (see include/feeds.mk in openwrt.git), so treat both
package managers the same way.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant