-
Notifications
You must be signed in to change notification settings - Fork 3
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
Comments
hm. i did a patch for this in another repo. Now... which one? |
As a temporary step, the following could be run as a 'post download' step to fix up the .right files:
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. |
Note the change 'find' above requires sedport (for the -i option) |
Running this change reduces the number of failures by 5 to 25.
|
heredoc.output has a similar issue with 'grep':
|
errors.output has a similar issue with 'Not a directory':
|
vredir.output has a similar issue with 'bad file descriptor':
|
exec.output has a similar issue with 'is a directory':
|
Running the updates above to add message numbers only reduces the number of failures by 1:
|
These are the new set of failures (as seen on zoscan2b):
Once it's reproduced on the CI machines, I will close off the issues for the newly passing tests |
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 testsThe text was updated successfully, but these errors were encountered: