Overview
Request 494879 accepted
- Update to 1.6
* Proper support for target communication via SSH has been added.
* A large number of very old config and baseboard files have been
removed. If you need to resurrect these, you can get them from
version 1.5.3. If you can show that a board is still in use,
it can be put back in the distribution.
* The --status command line option is now the default. This means
that any error in the testsuite Tcl scripts will cause runtest
to abort with exit status code 2. The --status option has been
removed from the documentation, but will continue to be
accepted for backward compatibility.
* runtest now exits with exit code 0 if the testsuite "passed",
1 if something unexpected happened (eg, FAIL, XPASS or
UNRESOLVED), and 2 if an exception is raised by the Tcl
interpreter.
* runtest now exits with the standard exit codes of programs that
are terminated by the SIGINT, SIGTERM and SIGQUIT signals.
* The user-visible utility procedures `absolute', `psource' and
`slay' have been removed. If a testsuite uses any of these
procedures, a copy of the procedure should be made and placed
in the lib directory of the testsuite.
* Support was added for testing the D compiler.
* ~/.dejagnurc is now loaded last, not first. This allows the
user to have the ability to override anything in their
environment (even the site.exp file specified by $DEJAGNU).
* The user-visible utility procedure `unsetenv' is deprecated
and will be removed in the next release. If a testsuite uses
any of these procedures, a copy of the procedure should be made
and placed in the lib directory of the testsuite.
- Run tests during build
Request History
rguenther created request
- Update to 1.6
* Proper support for target communication via SSH has been added.
* A large number of very old config and baseboard files have been
removed. If you need to resurrect these, you can get them from
version 1.5.3. If you can show that a board is still in use,
it can be put back in the distribution.
* The --status command line option is now the default. This means
that any error in the testsuite Tcl scripts will cause runtest
to abort with exit status code 2. The --status option has been
removed from the documentation, but will continue to be
accepted for backward compatibility.
* runtest now exits with exit code 0 if the testsuite "passed",
1 if something unexpected happened (eg, FAIL, XPASS or
UNRESOLVED), and 2 if an exception is raised by the Tcl
interpreter.
* runtest now exits with the standard exit codes of programs that
are terminated by the SIGINT, SIGTERM and SIGQUIT signals.
* The user-visible utility procedures `absolute', `psource' and
`slay' have been removed. If a testsuite uses any of these
procedures, a copy of the procedure should be made and placed
in the lib directory of the testsuite.
* Support was added for testing the D compiler.
* ~/.dejagnurc is now loaded last, not first. This allows the
user to have the ability to override anything in their
environment (even the site.exp file specified by $DEJAGNU).
* The user-visible utility procedure `unsetenv' is deprecated
and will be removed in the next release. If a testsuite uses
any of these procedures, a copy of the procedure should be made
and placed in the lib directory of the testsuite.
- Run tests during build
leaper added dejagnu as a reviewer
Submission for dejagnu by someone who is not maintainer in the devel project (devel:tools). Please review
leaper added leap-reviewers as a reviewer
leaper accepted review
ok
Andreas_Schwab accepted review
Ok
lnussel accepted review
lnussel_factory added openSUSE:Leap:42.3:Staging:A as a reviewer
Being evaluated by staging project "openSUSE:Leap:42.3:Staging:A"
lnussel_factory accepted review
Picked openSUSE:Leap:42.3:Staging:A
lnussel_factory accepted review
ready to accept
lnussel_factory approved review
ready to accept
lnussel_factory accepted request
Accept to openSUSE:Leap:42.3
openSUSE:Factory/dejagnu@25 -> openSUSE:Leap:42.3/dejagnu
expected origin is 'SUSE:SLE-12:GA' (changed)
the submitted sources are in or accepted for Factory
@rguenther: Will this change be making it in to SP3 or switching away from SLE to Factory version? cc @lnussel
I opened Fate#323428 internally but it would likely require an ECO at this point (fate targets both SP3 and SP4). It's just that upstream projects are considering making dejagnu 1.5 or later mandatory and we're stuck with ancient 1.4.