Re: Test harness on VMS working, 58 tests currently failing.
On 03/01/2014 09:50 PM, John E. Malmberg wrote: On 2/28/2014 8:07 PM, John E. Malmberg wrote: I have the test harness apparently working on VMS. I need to fix up the DCL command procedure that is needed set up a number of foreign commands needed by it before submitting a patch. For which version? I assume for the current development stream from the git repository, correct? If no one else is interested in immediately running the test harness on VMS, I can wait on submitting a patch until I determine what is causing all the test failures. So far running the test harness on VMS will require: Perl 5.18.1 or later. GNV 2.1.3 or later. Bash 4.2.45 or later. Coreutils 8.21 or later. From what I see, the tests are coded in perl. Can you give a short description for what the other stuff is needed? Investigation showed two additional VMS specific issues in the test harness that were affecting the test run. After fixing those issues: 69 Tests in 90 Categories Failed (See .diff* files in work dir for details) :-( As there were 126 log files created, this indicates that more tests were being run. I do not know why the category count changed. Still more than 1/2 the tests are failing. If I determine that a test failure is an actual bug in the VMS port instead of a feature of the implementation do you want tickets filed to track the issue, or just the the patch to fix it if it is possible to fix? If you have a patch, then I don't think a ticket is necessary. Otherwise a ticket is right thing to track the bug. ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
Re: Test harness on VMS working, 58 tests currently failing.
On 3/2/2014 6:11 AM, h.becker wrote: On 03/01/2014 09:50 PM, John E. Malmberg wrote: On 2/28/2014 8:07 PM, John E. Malmberg wrote: I have the test harness apparently working on VMS. I need to fix up the DCL command procedure that is needed set up a number of foreign commands needed by it before submitting a patch. For which version? I assume for the current development stream from the git repository, correct? This is for master of course. If no one else is interested in immediately running the test harness on VMS, I can wait on submitting a patch until I determine what is causing all the test failures. So far running the test harness on VMS will require: Perl 5.18.1 or later. GNV 2.1.3 or later. Bash 4.2.45 or later. Coreutils 8.21 or later. From what I see, the tests are coded in perl. Can you give a short description for what the other stuff is needed? The make scripts expect a number of GNU utilities to be present and for Perl to use UNIX filename syntax. The following commands are used by makefiles in the tests. ar, cat, cc, cp, diff, echo, false, mkdir, rm, sleep, sh, and touch. GNV provides the ar, and cc commands. I have not updated them yet. The bash in GNV is ancient and buggy. The Bash 4.2.45 is much more reliable. Coreutils supplies the rest of the utilities. While they are also supplied by GNV, the Coreutils kit is more up to date with significant bug fixes. Example: rm -rf actually works. It appears that GNU make on VMS is attempting to emulate touch. This is showing up in several test failures where the touch command is used in the makefile. So it looks like that emulation needs to be improved. So I will need to have a DCL procedure set these up as foreign commands temporarily before running the run_make_tests.pl. I have not yet finished that script. My plan get the tests that can be run to pass before merging in the GNV fork which runs the Bash shell from GNU Make. Regards, -John ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
Re: Test harness on VMS working, 58 tests currently failing.
On 2/28/2014 8:07 PM, John E. Malmberg wrote: I have the test harness apparently working on VMS. I need to fix up the DCL command procedure that is needed set up a number of foreign commands needed by it before submitting a patch. If no one else is interested in immediately running the test harness on VMS, I can wait on submitting a patch until I determine what is causing all the test failures. So far running the test harness on VMS will require: Perl 5.18.1 or later. GNV 2.1.3 or later. Bash 4.2.45 or later. Coreutils 8.21 or later. This limits running the test harness on Alpha/VMS 8.3 and 8.4 and IA64 VMS 8.4. 58 Tests in 103 Categories Failed (See .diff* files in work dir for details) :-( As there appears to be 111 log files, this is just less than half the tests passing. Investigation showed two additional VMS specific issues in the test harness that were affecting the test run. After fixing those issues: 69 Tests in 90 Categories Failed (See .diff* files in work dir for details) :-( As there were 126 log files created, this indicates that more tests were being run. I do not know why the category count changed. Still more than 1/2 the tests are failing. If I determine that a test failure is an actual bug in the VMS port instead of a feature of the implementation do you want tickets filed to track the issue, or just the the patch to fix it if it is possible to fix? Regards, -John ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
Test harness on VMS working, 58 tests currently failing.
I have the test harness apparently working on VMS. I need to fix up the DCL command procedure that is needed set up a number of foreign commands needed by it before submitting a patch. If no one else is interested in immediately running the test harness on VMS, I can wait on submitting a patch until I determine what is causing all the test failures. So far it will require: Perl 5.18.1 or later. GNV 2.1.3 or later. Bash 4.2.45 or later. Coreutils 8.21 or later. This limits running the test harness on Alpha/VMS 8.3 and 8.4 and IA64 VMS 8.4. 58 Tests in 103 Categories Failed (See .diff* files in work dir for details) :-( As there appears to be 111 log files, this is just less than half the tests passing. I still need to investigate all of these failures. The features/archives test fails because the GNV AR utility requires real VMS object files at this time, and the test just creates some files. I will need to adjust the test setup section for VMS. Some of the other tests are failing because the VMS sets argv[0] differently than what is expected. I have a fix from the Bash 4.2.45 port that will handle that. 3 tests timed out after 5 seconds. Here is an example of a passing test. EAGLE perl run_make_tests.pl features/comments -- Running tests for GNU make on VMS GNU Make 4.0.90 -- Clearing /lcl_root/make/tests/work... Making work dirs... features/comments ... ok (1 passed) 1 Test in 1 Category Complete ... No Failures :-) Regards, -John ___ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make