From: Rocky B. <ro...@gn...> - 2017-06-04 13:39:08
|
Thanks - I'll look at this when I get a chance. Some general information and then some general questions. The failing integration tests look are the tests that are most fragile and can change with bash release. Generally it's nothing serious, in that it is the test that is wrong, not the functioning of bashdb. To verify this belief, look at the file test/integration/test-suite.log as the above output suggests. You should see diff-style output showing what was expected and what you got instead. Send it to me directly and I'll look. Just today earlier I was working on detecting the terminal background and whether it was dark or light, and I recall a lot of failures in the same files listed above. Most of what I had to do was make sure to pass the - -no-highlight option in the tests to make output checking more predictable. The kinds if differences I was seeing was in adding ansi escape sequences for marking the output that I was getting but wasn't expected. Are you working off of sourceforge git or the last release? If git, make sure to "git pull" since this changed a little while ago. The other place where tests start failing is on a new release (from bashdb's standpoint) of bash. I am not sure I have tried version 4.4 yet. (I might have but I don't remember) Is this the first time you've tried bashdb with bash version 4.4? With bash 4.3 that works, right? On Sun, Jun 4, 2017 at 9:03 AM, jean-christophe manciot < act...@gm...> wrote: > distribution: Ubuntu Zesty > bash sources: https://packages.debian.org/source/stretch/bash > bash version: 4.4.12(1) (built from latest debian 4.4-5) > bashdb sources: git://git.code.sf.net/p/bashdb/code > bashdb commit: 4e1479d18829a4de1081b936a4976ac534007016 > bashdb configure options: > --with-bash-src=/home/actionmystique/src/Bash/bash-4.4-5 \ > --build=x86_64-pc-linux-gnu \ > --prefix=/usr --sysconfdir=/etc > --localstatedir=/var \ > --infodir=/usr/share/info > --mandir=/usr/share/man > bashdb build tool: remake --trace > bashdb check tool: make check > bashdb tests log: attached test/integration/test-suite.log > > PASS: test-bug-step-subshell > FAIL: test-complete > PASS: test-debug > PASS: test-delete > PASS: test-export > PASS: test-file-with-spaces > PASS: test-info-args > FAIL: test-interrupt > PASS: test-misc > PASS: test-setshow > FAIL: test-sig > PASS: test-action > PASS: test-brkpt > PASS: test-bug-args > PASS: test-bugI > PASS: test-bugIFS > PASS: test-bug-loc > PASS: test-bug-source > PASS: test-command > PASS: test-display > PASS: test-enable > PASS: test-finish > PASS: test-frame > PASS: test-list > FAIL: test-lopts > PASS: test-multi > PASS: test-parm > PASS: test-restart > PASS: test-search > FAIL: test-settrace > PASS: test-skip > FAIL: test-sopts > FAIL: test-bug-break > PASS: test-bug-clear > PASS: test-bug-step > PASS: test-subshell > PASS: test-tbreak > FAIL: test-trace > PASS: test-watch1 > PASS: test-watch2 > ============================================================ > ================ > Testsuite summary for bashdb 4.4-0.92 > ============================================================ > ================ > # TOTAL: 42 > # PASS: 33 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 9 > # XPASS: 0 > # ERROR: 0 > ============================================================ > ================ > See test/integration/test-suite.log > Please report to bas...@li... > ============================================================ > ================ > > -- > Jean-Christophe > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Bashdb-devel mailing list > Bas...@li... > https://lists.sourceforge.net/lists/listinfo/bashdb-devel > |