From: chrubis@suse.cz
To: Mats Liljegren <mats.liljegren@enea.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Design question around ltp-list
Date: Mon, 17 Mar 2014 17:23:06 +0100 [thread overview]
Message-ID: <20140317162305.GA2215@rei> (raw)
In-Reply-To: <0247700D01F14443B9209F90AD938CC524366738@sestoex05.enea.se>
Hi!
> That means I get no support for errors occurring when executing the
> load, i.e. I have to check the return value myself and give correct
> diagnostic message. Not a real problem, just more work to do...
That is mostly one waitpid() in parent, you don't have to overdo the
error conditions checks. There is always possibility that something
unexpected will happen. The most appropripate behavior is to fail the
test and expect user to check what has happened.
> But now I know I should avoid ltp-pan, thanks!
I'm not even sure that running pan from pan would work fine. There is
really tricky stuff with terminal controll and sessions that allows it
to kill test leftover processes which may cause really strange behavior.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-03-17 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 10:11 [LTP] Design question around ltp-list Mats Liljegren
2014-03-17 12:39 ` Carlos Hernandez
2014-03-17 13:56 ` chrubis
[not found] ` <0247700D01F14443B9209F90AD938CC524366738@sestoex05.enea.se>
2014-03-17 16:23 ` chrubis [this message]
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=20140317162305.GA2215@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=mats.liljegren@enea.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