Re: [GnuCOBOL 3.1-rc1] testsuite: 23 335 744 757 failed

[Pedro Oliveira]

Hello Simon,

Thank you for the quick reply.

Since I am following a tutorial from 2016, I kind of expected the library to be on a different version. I have been able to work with it for now. And since the other tutorials are from 2020, with WSL, I don't think this may a problem in the future.

Kind regards

---
Pedro André Oliveira

t: +351 916 175 642
m: pedro.andre.oliveira@outlook.com

Japonês Nível 4 (ECJP4) & JLPT (N5)
Faculdade de Letras da Universidade do Porto (FLUP)

Mestrado Integrado em Engenharia Informática e Computação (MIEIC)
Faculdade de Engenharia da Universidade do Porto (FEUP)

On Wed, Oct 28, 2020 at 3:37 PM Simon Sobisch <simonsobisch@web.de> wrote:

Hi Pedro and welcome to GnuCOBOL.

Also thank you for sending in the test results.

`make check` lists four unexpected results:

  23: used_binaries.at:715 run job after compilation from stdin
      runmisc cobc cobcrun
 335: syn_misc.at:6911   very long literal in error message
      misc literals
 744: run_file.at:4857   SEQUENTIAL file with SHARING READ ONLY
      runfile
 757: run_file.at:5762   INDEXED file with LOCK AUTOMATIC (2)
      runfile

The first two seem to be solved in 3.1-dev already and the other two are
"old" issues in the cygwin environment, related to file locking.

Most cygwin environments are single-user, so those two may not have a
consequence for you. In general Cygwin is only suggested to be used if
you are a Cygwin user in any case, otherwise you may want to have a look
at the official MinGW packages [1].

In general I'd consider your build (other than a _potential_ locking
issue with concurrent access to the same file) good to use.

Simon

[1]: https://nam11.safelinks.protection.outlook.com/?url="">

Am 28.10.2020 um 14:49 schrieb Pedro Oliveira:
> Hello,
>
> I have recently started working with Cobol and during the setup, "make
> check" returned the following errors in attachment.
>
> Kind regards,
> Pedro