This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "DejaGNU".

The branch, master has been updated
       via  1f6b2171a1f602f58fb9f03c987569a94b629a9f (commit)
       via  dbc8ec89d17c2055884b332be9ea5c5a63c616ad (commit)
      from  df37452fa640af0479c1533fd81c7235a92da2ff (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 1f6b2171a1f602f58fb9f03c987569a94b629a9f
Author: Joseph Myers <[email protected]>
Date:   Tue Mar 24 21:21:21 2026 +0000

    ssh.exp: force pty allocation in ssh_exec
    
    There are some GCC tests that use dg-output and depend on correct
    interleaving of stdout and stderr, which only works correctly when the
    test program is run in a pty.

commit dbc8ec89d17c2055884b332be9ea5c5a63c616ad
Author: Joseph Myers <[email protected]>
Date:   Tue Mar 24 21:20:55 2026 +0000

    ssh.exp: do not use '&&' with 'XYZ${?}ZYX' logic
    
    There is a bogus comment "We use && here, as otherwise the echo always
    works, which makes it look like execution succeeded when in reality it
    failed.".  But the whole point of the XYZ${?}ZYX logic, taken from
    rsh.exp, is that code a few lines below uses a regular expression to
    extract the actual exit status from the test output, which the use of
    '&&' breaks when the test program does fail.  Furthermore, if the
    intent was to yield nonzero exit status from local_exec when the test
    program fails, the subsequent rm would prevent that from working by
    yielding the exit status from rm instead.

-----------------------------------------------------------------------

Summary of changes:
 lib/ssh.exp | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)


hooks/post-receive
-- 
DejaGNU

_______________________________________________
Dejagnu-commit mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/dejagnu-commit

Reply via email to