kselftest/tty: Report a consistent test name for the one test we runCurrently the tty_tstamp_update test reports a different exit messagefor every path it can exit via. This can be confusing for a
kselftest/tty: Report a consistent test name for the one test we runCurrently the tty_tstamp_update test reports a different exit messagefor every path it can exit via. This can be confusing for automated systemsas the string that gets logged is interpreted as a test name so if the teststatus changes they can't tell that it's the same test case that was run,they can see that the overall status of the test program is a failure butit's not clear that it was running the same test.Change all the messages that are logged to be diagnostic prints and log thename of the program as the test name.Signed-off-by: Mark Brown <broonie@kernel.org>Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
show more ...
selftests: tty: add selftest for tty timestamp updatesAdd new test case which checks that timestamp updates on actual terminalcharacter device (e.g. /dev/pts/0) happen even if the terminal isacce
selftests: tty: add selftest for tty timestamp updatesAdd new test case which checks that timestamp updates on actual terminalcharacter device (e.g. /dev/pts/0) happen even if the terminal isaccessed via magic /dev/tty file.Signed-off-by: Michal Sekletar <msekleta@redhat.com>Message-ID: <20230613172107.78138-2-msekleta@redhat.com>Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>