zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Valgrind tests (was: Re: Zsh: [7] + 23074 suspended (tty output))
Date: Tue, 18 Sep 2018 15:55:39 +0000	[thread overview]
Message-ID: <1537286139.1154549.1512322472.101174D6@webmail.messagingengine.com> (raw)
In-Reply-To: <CAKc7PVD0aoqenFzNeo-3HitqAtxi27-t=EcNQwc4=t57SYs0Hg@mail.gmail.com>

Sebastian Gniazdowski wrote on Tue, 18 Sep 2018 07:21 +0200:
> On Mon, 17 Sep 2018 at 16:50, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> 
> > Can you describe what changes would be involved?  Would the test
> > suite remain as portable as it should be?
> 
> I was thinking little different back then when creating VATS, it
> appeared reasonable to have separate tests aimed at stressing Zsh in
> terms of memory usage, etc. I now see that the main Zsh tests are
> putting much stress on Zsh, so VATS should just add vtest.conf, custom
> runtests.zsh, zsh-valgrind-parse.cmd, custom ztst.zsh (I'm not sure if
> the two custom files really have to be different), from here:
> https://github.com/zdharma/VATS-zsh/tree/master/VATS.

You haven't actually answered my question.  Can you, please, explain
what changes would need to be made to zsh in order to implement your
upthread proposal?  It's fine to link to external sources for details
but the gist should be self-contained and understandable by readers
familiar with zsh and its build system but nothing else.

> The readme of this project is unnecessarily very long, the thing is
> very simple, I need some time to approach this again with original
> Test/ in mind.

For avoidance of doubt, I am simply asking for information on the
proposal.  I am not yet sold on it.

  reply	other threads:[~2018-09-18 15:56 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   ` Valgrind tests (was: Re: Zsh: [7] + 23074 suspended (tty output)) Daniel Shahaf
2018-09-18  5:21     ` Sebastian Gniazdowski
2018-09-18 15:55       ` Daniel Shahaf [this message]
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=1537286139.1154549.1512322472.101174D6@webmail.messagingengine.com \
    --to=d.s@daniel.shahaf.name \
    --cc=sgniazdowski@gmail.com \
    --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).