adjustment of CI - testing

[GitMensch]

@ddeclerck @lefessan would you mind to go on with the work done in 5cc12e16b0dbfe8117332eee790f3866f6bb6fe6? Things to consider:

• running make check on all workers that don't use the next
• on the fastest CI, which I assume to be the GNU/Linux worker;
  • running make distcheck TESTSUITEFLAGS="--jobs= $(($(nproc)+1))" - this will:
  • verify that distribution files can be created (you possibly would need to add more software dependencies, especially related to PDF generation)
  • verify that added files are distributed correctly
  • VPATH builds work
  • the internal testuite still passes
  • and create the source distribution tarball (if you want a different and/or more formats than tar.gz pass an additional DIST_TARGETS="distbin-gzip distbin-lzip dist-xz" to make distcheck`)
  • make the resulting gnucobol*.tar.gz available as artifact for download
• run the NIST85 testsuite (you likely would cache newcob.val.Z / newcobl.val.tar.gz for that cd tests/cobo85 && make EXEC85 && make --jobs=$(($(nproc)+1)) test

[nberth]

@GitMensch At the moment we have in #41 three workflows for "common" platforms (although I admit I should substitute debian for ubuntu, to include at least one somewhat more "free-leaning" system.) The current workflows provide some archive of testsuite logs in case some of the tests fail (this still excludes the NIST85 testsuite); these artifacts are available for download on the summary page for the corresponding actions. The ubuntu workflow also provides a distribution archive artifact.

Note there are some issues with the tests on windows and macos platforms. Some of these failures seem related to directory prefix passed (or not) to the configure script.

[GitMensch]

All of those issues are fixed now, but for some reason the Ubuntu and MacOS workflows were manually disabled?

[nberth]

Indeed I manually disabled them while testing. Now everything should be fine.

[GitMensch]

Somehow the windows "check" seems to hang: https://github.com/OCamlPro/gnucobol/runs/7237227459?check_suite_focus=true

I suggest aborting this one, then manually starting Ubuntu + MacOS workflow via Action tab, then starting the Windows one again.

[nberth]

Not sure what's happening with that issue on windows; is there a way to adjust the on: field so it can only be launched manually?.

[GitMensch]

Not sure what's happening with that issue on windows; is there a way to adjust the on: field so it can only be launched manually?.

Just drop everything but the manual one?

 on:
-  pull_request:
-    branches: [ gcos4gnucobol-3.x ]
-  push:
  # manual run in actions tab - for all branches
  workflow_dispatch:

I guess.

[nberth]

During some tests yesterday I though there was actually some defaults for this field. But in the end I think it was just me being confused by the impact of the workflows on this repository w.r.t my own fork.