public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Stefan Liebler <stli@linux.ibm.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v7] posix: Add terminal control setting support for posix_spawn
Date: Thu, 27 Jan 2022 11:52:20 +0000	[thread overview]
Message-ID: <20220127115220.GE1989194@arm.com> (raw)
In-Reply-To: <475ee880-5f93-0c71-96f7-f8ea303aafed@linux.ibm.com>

The 01/27/2022 09:27, Stefan Liebler via Libc-alpha wrote:
> On 24/01/2022 22:52, Carlos O'Donell via Libc-alpha wrote:
> > and posix_spawnattr_tcgetpgrp_np.
> > The function sets a new attrib
> 
> Hi Adhemerval,
> 
> I'm getting an error with the new posix/tst-spawn6 testcase.
> 
> When running the test in an interactive shell, the test passes:
> $ cd <build-dir>
> $ make t=posix/tst-spawn6 test
> PASS: posix/tst-spawn6
> original exit status 0
> 
> When running it e.g. as ssh-command or as cron-job, the test fails:
> $ ssh localhost "cd <build-dir>; make t=posix/tst-spawn6 test;"
> FAIL: posix/tst-spawn6
> original exit status 1
> error: xopen.c:28: open64 ("/dev/tty", 0x0, 0600): No such device or address
> error: 1 test failures
> 
> The failing open is the first one executed in do_test.
> 
> Would it make sense to mark the test UNSUPPORTED in this case?

note: i see the same error when i run the test
in a container without a tty.

(i now added --tty to my docker run command)

  parent reply	other threads:[~2022-01-27 11:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 18:10 Adhemerval Zanella
2022-01-24 21:52 ` Carlos O'Donell
2022-01-27  8:27   ` Stefan Liebler
2022-01-27 11:40     ` Adhemerval Zanella
2022-01-27 11:52     ` Szabolcs Nagy [this message]
2022-01-26 17:44 ` Joseph Myers
2022-01-26 19:06   ` Adhemerval Zanella

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220127115220.GE1989194@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=libc-alpha@sourceware.org \
    --cc=stli@linux.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).