GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Run the upstream testsuite against our code in the CI · Issue #8 · uutils/diffutils

Run the upstream testsuite against our code in the CI #8

New issue
Copy link
New issue
Copy link
Closed
Closed
Run the upstream testsuite against our code in the CI#8
Copy link

Description

@sylvestre
sylvestre
opened on Jan 27, 2024
Issue body actions

Upstream tests are here:
https://git.savannah.gnu.org/cgit/diffutils.git/tree/tests

Activity

  1. oSoMoN commented on Feb 9, 2024

    @oSoMoN
    oSoMoN
    on Feb 9, 2024
    Collaborator
    More actions

    I'm looking into that one.
    WIP at https://github.com/oSoMoN/uutils-diffutils/tree/run-upstream-testsuite.

  2. sylvestre commented on Feb 11, 2024

    @sylvestre
    sylvestre
    on Feb 11, 2024
    SponsorCollaboratorAuthor
    More actions

    thanks
    note we have these:
    https://github.com/uutils/coreutils/blob/main/util/run-gnu-test.sh
    https://github.com/uutils/coreutils/blob/main/util/build-gnu.sh

  3. oSoMoN commented on Feb 11, 2024

    @oSoMoN
    oSoMoN
    on Feb 11, 2024
    Collaborator
    More actions

    Thanks for the pointers. I initially intended to do something similar, but the overhead of bootstrapping the upstream code base, then running configure, then building the upstream binaries, to merely run shell scripts in the tests/ subdirectory is dissuasive. On my development machine, which is reasonably powerful, it takes a significant amount of time and CPU power to do all that, and it runs a ton of checks that are irrelevant to running the tests. And as far as I can tell there is no option to skip most of the configure checks and building the upstream binaries.

    Hence my approach to only check out the tests subdirectory, and run the tests manually. This probably isn't perfect, but it is lightweight and fast, and it will spare local resources as well as github action runners' resources.

  4. sylvestre
    closed this as completedin 790ef1eon Feb 17, 2024
  5. oSoMoN
    added a commit that references this issue on Feb 21, 2024

    Run the GNU test suite in CI (fixes uutils#8) (uutils#13)

    This issue will close once commit 790ef1e is merged into the 'main' branch.
    790ef1e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.