make[2]: Working in:
/usr/ports/devel/bashdb/work/bashdb-4.4-1.0.1/test/integration
^Cmake[4]: test-interrupt.log removed Error code 130 Signal 2 Signal 2 Signal 2 Signal 2
leads me to believe that none of the integration tests are working.
When you cd into test/integration and run
$ make clean && for t in test-*; do echo $t; bash $t; done
what is the output. In other words are integration tests working that way?
Status: open Group: v1.0_(example) Labels: bash5 patch Created: Mon Jan 14, 2019 09:02 AM UTC by ehaupt Last Updated: Mon Jan 14, 2019 11:27 AM UTC Owner: nobody Attachments:
The tests that end in .in don't actually get run. (Writing more shell code
you could exclude those, but I was lays). So the messages involve @sed@
and @grep@ or missing right files are an artifact that those are not real
tests. In the log there were no real errors yet, before you stopped this
early.
Status: open Group: v1.0_(example) Labels: bash5 patch Created: Mon Jan 14, 2019 09:02 AM UTC by ehaupt Last Updated: Wed Jan 16, 2019 06:01 PM UTC Owner: nobody Attachments:
I wonder if there is more to it than this. I don't have bash 5.0 installed. Would you run
and attach the console output?
You'll also have to re-generate 'configure' with the autotools, but once you have you'll get (see attachment).
Make check does not finish. It hangs after:
make check-TESTS
PASS: test-bug-step-subshell
PASS: test-bug-set-e
PASS: test-complete
PASS: test-debug
PASS: test-delete
PASS: test-export
SKIP: test-file-with-spaces
PASS: test-info-args
Pressing ^C - t you get:
load: 0.43 cmd: sleep 44574 [nanslp] 0.52r 0.00u 0.00s 0% 2132k
make: Working in: /usr/ports/devel/bashdb/work/bashdb-4.4-1.0.1
make[1]: Working in: /usr/ports/devel/bashdb/work/bashdb-4.4-1.0.1/test
make[4]: Working in: /usr/ports/devel/bashdb/work/bashdb-4.4-1.0.1/test/integration
make[3]: Working in: /usr/ports/devel/bashdb/work/bashdb-4.4-1.0.1/test/integration
make[2]: Working in: /usr/ports/devel/bashdb/work/bashdb-4.4-1.0.1/test/integration
This:
make[2]: Working in:
/usr/ports/devel/bashdb/work/bashdb-4.4-1.0.1/test/integration
^Cmake[4]: test-interrupt.log removed
Error code 130
Signal 2
Signal 2
Signal 2
Signal 2
leads me to believe that none of the integration tests are working.
When you cd into test/integration and run
$ make clean && for t in test-*; do echo $t; bash $t; done
what is the output. In other words are integration tests working that way?
On Wed, Jan 16, 2019 at 1:01 PM ehaupt ehaupt@users.sourceforge.net wrote:
Here's what I get (attachment). Definitely looks like more work is needed for 5.0.
Close this PR, open a new one titled "[Feature Request] support bash 5.0"?
The tests that end in .in don't actually get run. (Writing more shell code
you could exclude those, but I was lays). So the messages involve @sed@
and @grep@ or missing right files are an artifact that those are not real
tests. In the log there were no real errors yet, before you stopped this
early.
On Wed, Jan 16, 2019 at 3:43 PM ehaupt ehaupt@users.sourceforge.net wrote:
Bash was also updated to version 5 in Slackware, so I am also seing this problem.
I patched the configure script to ignore the version, but this doesn't make bashdb more stable.
In commit f2f889c in the bash 5.0 branch I have started to update for bash 5.0. Please see if this addresses the problems.
Last edit: Rocky Bernstein 2019-09-02
Ticket moved from /p/bashdb/bugs/59/