zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Valgrind tests (was: Re: Zsh: [7] + 23074 suspended (tty output))
Date: Mon, 17 Sep 2018 14:49:33 +0000	[thread overview]
Message-ID: <1537195773.3258650.1510860136.6AA9F0BA@webmail.messagingengine.com> (raw)
In-Reply-To: <CAKc7PVAsJXv=jxcbrENM4LtcBkz86mbVe3WgCYBs6cwdEO=9hQ@mail.gmail.com>

Sebastian Gniazdowski wrote on Mon, 17 Sep 2018 16:01 +0200:
> Hello
> Allow me to do this broken record writing, but wouldn't it be nice to
> have Valgrind automatic tests prepared for a handy run while doing the
> `suspended tty' investigation and patching? The VATS (Valgrind
> Automatic Tests Suite) can be still added to upstream. It is just a
> copy of Test directory, I know this doesn't sound nice, but also:
> definition-files with non-harmful, already known Valgrind errors, and
> a Zsh script that parses Valgrind output doing some hiding,
> formatting, etc.

Yes, it would be a good thing to have support in the build system to run
the test suite under valgrind, complete with developer documentation
(such as what configure and config.modules settings to use).

However, if the proposal means having two copies of the Test/ directory,
then it's a non-starter.

Can you describe what changes would be involved?  Would the test
suite remain as portable as it should be?

Cheers,

Daniel

  reply	other threads:[~2018-09-17 14:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15 17:22 Zsh: [7] + 23074 suspended (tty output) TS
2018-09-15 18:10 ` Bart Schaefer
2018-09-15 18:51   ` TS
2018-09-15 19:06     ` TS
2018-09-16  8:40       ` Vincent Lefevre
2018-09-16 15:40         ` TS
2018-09-16 17:51           ` Peter Stephenson
2018-09-17 20:13           ` TS
2018-09-18 17:59             ` Peter Stephenson
2018-09-18  1:16         ` Vincent Lefevre
2018-09-18 17:58           ` Peter Stephenson
2018-09-20 12:01             ` Vincent Lefevre
2018-09-20 16:11               ` Daniel Shahaf
2018-09-18 19:30           ` TS
2018-09-19  3:38             ` TS
2018-09-19 14:23               ` Daniel Tameling
2018-09-19 16:12               ` Peter Stephenson
2018-09-19 18:15                 ` TS
2018-09-17 14:01 ` Sebastian Gniazdowski
2018-09-17 14:49   ` Daniel Shahaf [this message]
2018-09-18  5:21     ` Valgrind tests (was: Re: Zsh: [7] + 23074 suspended (tty output)) Sebastian Gniazdowski
2018-09-18 15:55       ` Daniel Shahaf
2018-09-19  5:04         ` Sebastian Gniazdowski
2019-07-03 23:29         ` Sebastian Gniazdowski
2019-07-03 23:31           ` Sebastian Gniazdowski
2019-07-03 23:45             ` Sebastian Gniazdowski
2019-07-13 14:31               ` Sebastian Gniazdowski
2019-07-14  6:39                 ` Daniel Shahaf
2019-07-14 22:17                   ` Sebastian Gniazdowski
2019-07-15  8:54                     ` Peter Stephenson
2019-07-15  9:29           ` Peter Stephenson
2019-07-15 18:45             ` Sebastian Gniazdowski

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=1537195773.3258650.1510860136.6AA9F0BA@webmail.messagingengine.com \
    --to=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).