Skip to content
Snippets Groups Projects
  1. Sep 02, 2023
    • Jeffery To's avatar
      CI: Fix finding test script · 369511a2
      Jeffery To authored
      
      Currently, the run-test code tries to find the package source directory
      based on the directory name only. This fails for the Go compiler package
      because there is more than one directory named "golang".
      
      This uses the full path listed in the "Source:" line of the control file
      to find the package source directory.
      
      This also:
      
      * Checks for the test script earlier, to avoid installing and removing
        ipk files when there is no test script to be run
      
      * Makes PKG_VERSION parsing more lenient, as the package may not have a
        PKG_RELEASE, e.g. attendedsysupgrade-common
      
      Signed-off-by: default avatarJeffery To <jeffery.to@gmail.com>
      (cherry picked from commit 5422bd621836e361bcb49c427f888fe3a8df267c)
      369511a2
  2. Jun 19, 2023
  3. Jun 15, 2023
  4. May 10, 2023
  5. May 01, 2023
  6. Apr 19, 2023
    • Jeffery To's avatar
      CI: Add local feed for CI-built packages · e9bb9484
      Jeffery To authored
      
      To test each package, the CI-built target package (ipk) file is
      installed, but currently the target package's dependencies are installed
      from the standard opkg feeds.
      
      There are cases when the CI-built target packages should be
      installed/tested together:
      
      * If a pull request contains several new packages that depend on each
        other, the test step will fail as the new dependencies cannot be found
        in the current packages feed.
      
      * If a pull request upgrades a source package that builds several target
        packages that depend on each other, the test step may fail due to the
        version/ABI mismatch between a newer target package and the older
        dependencies installed from the packages feed.
      
      This sets up a local feed for the CI-built packages so that dependencies
      are also installed from the same set of packages.
      
      Signed-off-by: default avatarJeffery To <jeffery.to@gmail.com>
      Unverified
      e9bb9484
  7. Mar 22, 2023
    • Jeffery To's avatar
      CI: Add --autoremove, ignore removal errors · f0d5e470
      Jeffery To authored
      836b4e1c added
      --force-removal-of-dependent-packages but it does not do what the commit
      message says it does.
      
      When package A depends on package B (package B is a dependency of
      package A; package A is a dependent of package B), trying to remove
      package B while package A is installed will result in an error. Adding
      --force-removal-of-dependent-packages in this case will cause the
      removal of package B and package A (package B's dependent).
      
      But in the case of the CI testing step, it is package A that is being
      installed and removed. Removing package A with
      --force-removal-of-dependent-packages will not cause package B (package
      A's dependency) to be removed.
      
      This adds --autoremove to actually remove the package's dependencies.
      
      This also ignores any errors returned by opkg remove as --autoremove can
      sometimes falsely return an error[1].
      
      [1]: https://github.com/openwrt/openwrt/issues/12241
      
      
      
      Fixes: 836b4e1c ("github-ci: add --force-removal-of-dependent-packages")
      Signed-off-by: default avatarJeffery To <jeffery.to@gmail.com>
      Unverified
      f0d5e470
  8. Mar 13, 2023
  9. Feb 03, 2023
  10. Dec 08, 2022
  11. Dec 02, 2022
  12. Nov 27, 2022
  13. Oct 25, 2022
  14. May 31, 2022
  15. May 18, 2022
  16. May 16, 2022
  17. May 15, 2022
  18. May 07, 2022
  19. Mar 24, 2022
  20. Jan 15, 2022
  21. Jan 14, 2022
  22. Nov 09, 2021
  23. Nov 05, 2021
  24. Oct 10, 2021
  25. Oct 09, 2021
  26. Sep 28, 2021
  27. Mar 28, 2021
  28. Mar 26, 2021
    • Paul Spooren's avatar
      CI: revert adding of *depending* packages · a2bda4cc
      Paul Spooren authored
      
      While the idea may make sense the current implementation is faulty.
      Problem is that OpenWrt uses the folder name of packages within the
      build system while `opkg` spits out the actual packages names.
      
      An example, compiling the packages of folder `vim` (`make
      package/vim/compile`) creates a package called `xxd`, where `make
      package/xxd/compile` would fail.
      
      The current implementation uses `opkg` to figure out dependent packages,
      but the resulting names do not match the above mentioned folders.
      
      Revert this for now until we come up with a better implementation to
      avoid false positive CI failures.
      
      Signed-off-by: default avatarPaul Spooren <mail@aparcar.org>
      a2bda4cc
  29. Mar 23, 2021
Loading