Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General issue to track failing tests in bash test suite #3

Open
IgorTodorovskiIBM opened this issue Oct 31, 2022 · 12 comments
Open

General issue to track failing tests in bash test suite #3

IgorTodorovskiIBM opened this issue Oct 31, 2022 · 12 comments
Labels
help wanted Extra attention is needed

Comments

@IgorTodorovskiIBM
Copy link
Collaborator

Many tests are failing because there is a discrepancy in the error messages:
EDC5129I No such file or directory
vs
No such file or directory

We may need to create a platform specific *.right file for some tests

@IgorTodorovskiIBM IgorTodorovskiIBM added the help wanted Extra attention is needed label Oct 31, 2022
@MikeFultonDev
Copy link
Collaborator

hm. i did a patch for this in another repo. Now... which one?

@MikeFultonDev
Copy link
Collaborator

MikeFultonDev commented Dec 24, 2022

Similar patches in m4 and autoconf (see m4 and autoconf)

@MikeFultonDev
Copy link
Collaborator

MikeFultonDev commented Dec 24, 2022

As a temporary step, the following could be run as a 'post download' step to fix up the .right files:

find . -type f -name "*.right" -exec sed -i 's/No such file or directory/EDC5129I No such file or directory./' {} \;

An alternate would be to run the script and then generate patch files. If the comparison is 'smart' and accepts regular expressions then perhaps we can add some sort of [A-Z0-9]* type of addition (and then deal with the trailing period we decided to issue) so that we can make the 'right' file generic.

@MikeFultonDev
Copy link
Collaborator

Note the change 'find' above requires sedport (for the -i option)

@MikeFultonDev
Copy link
Collaborator

MikeFultonDev commented Dec 24, 2022

Running this change reduces the number of failures by 5 to 25.

tests/exp.output
tests/ifs.output
tests/heredoc.output
tests/posixpat.output
tests/read.output
tests/redir.output
tests/shopt.output
tests/test.output
tests/coproc.output
tests/errors.output
tests/posixexp.output
tests/printf.output
tests/procsub.output
tests/trap.output
tests/varenv.output
tests/vredir.output
tests/builtins.output
tests/exec.output
tests/history.output
tests/lastpipe.output
tests/nquote.output
tests/dynvar.output
tests/histexp.output
tests/intl.output
tests/new-exp.output

@MikeFultonDev
Copy link
Collaborator

heredoc.output has a similar issue with 'grep':

< grep: FSUM6003 input file "*.c": EDC5129I No such file or directory.
---
> grep: *.c: EDC5129I No such file or directory

@MikeFultonDev
Copy link
Collaborator

errors.output has a similar issue with 'Not a directory':

< ./errors.tests: line 193: cd: /bin/sh: EDC5135I Not a directory.
---
> ./errors.tests: line 193: cd: /bin/sh: Not a directory

@MikeFultonDev
Copy link
Collaborator

vredir.output has a similar issue with 'bad file descriptor':

103c101
< ./vredir8.sub: line 12: $fd: EDC5113I Bad file descriptor.
---
> ./vredir8.sub: line 12: $fd: Bad file descriptor

@MikeFultonDev
Copy link
Collaborator

exec.output has a similar issue with 'is a directory':

< ./execscript: line 40: /: EDC5123I Is a directory.
---
> ./execscript: line 40: /: Is a directory
16c16
< /: /: EDC5123I Is a directory.
---
> /: /: Is a directory

@MikeFultonDev
Copy link
Collaborator

Running the updates above to add message numbers only reduces the number of failures by 1:

tests/exp.output
tests/ifs.output
tests/heredoc.output
tests/posixpat.output
tests/read.output
tests/redir.output
tests/shopt.output
tests/test.output
tests/coproc.output
tests/posixexp.output
tests/printf.output
tests/procsub.output
tests/trap.output
tests/varenv.output
tests/vredir.output
tests/builtins.output
tests/exec.output
tests/history.output
tests/lastpipe.output
tests/nquote.output
tests/dynvar.output
tests/histexp.output
tests/intl.output
tests/new-exp.output

@MikeFultonDev
Copy link
Collaborator

MikeFultonDev commented Dec 28, 2022

adding diffutils, findutils, od (from coreutils), sed to set of tools and building from scratch reduces failures:

Issues opened:

tests/heredoc.output (8)
tests/read.output (17)
tests/redir.output (19, 20)
tests/test.output (22)
tests/coproc.output (20, 23) [no longer failing]
tests/glob.output (25)
tests/exec.output (11)
tests/procsub.output (26) [no longer failing]
tests/trap.output (11)
tests/varenv.output (11)
tests/vredir.output (28, 29)
tests/builtins.output (12)
tests/lastpipe.output (30)
tests/histexp.output (30)
tests/intl.output (31)
tests/new-exp.output (16)

@MikeFultonDev MikeFultonDev changed the title Update tests to consider z/OS error code (EDC5129I No such file or directory) vs (No such file or directory) General issue to track failing tests in bash test suite Dec 28, 2022
@IgorTodorovskiIBM
Copy link
Collaborator Author

These are the new set of failures (as seen on zoscan2b):

tests/heredoc.output
tests/read.output
tests/redir.output
tests/glob.output
tests/printf.output
tests/trap.output
tests/varenv.output
tests/vredir.output
tests/exec.output
tests/builtins.output
tests/intl.output
tests/new-exp.output

Once it's reproduced on the CI machines, I will close off the issues for the newly passing tests

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants