public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v5 1/1] syscalls/mq_open: fix old tests + convert to use new API
Date: Mon, 23 Jan 2017 17:07:50 +0100	[thread overview]
Message-ID: <20170123160750.GH25788@rei.lan> (raw)
In-Reply-To: <20170119153603.26881-1-pvorel@suse.cz>

Hi!
Pushed with cosmetic changes, removed the now unused enum and fixed a
few over 80 character lines, thanks.

> ---
> Note about parsing results, there are too many cases (well there are quite a
> lot of tests). I used your version (added missing TPASS at the end). I have to
> say, I'd still prefer more complicated if stacement and less duplicity),
> something like this:
> 
> if (TEST_ERRNO != tc->err) {
> 	tst_res(TFAIL | TTERRNO, "%s unexpectedly expected errno: %d", tc->desc,
> 			TEST_ERRNO);
> 	goto CLEANUP;
> }
> 
> if ((tc->ret == 0 && TEST_RETURN < 0) ||
> 	(tc->ret < 0 && TEST_RETURN != tc->ret))
> 	tst_res(TFAIL | TTERRNO, "%s wrong return code: %ld", tc->desc,
> 			TEST_RETURN);
> else
> 	tst_res(TPASS | TTERRNO, "%s returned: %ld", tc->desc, TEST_RETURN);

This one is not that bad, but I still prefer the more verbose one.

As far as code readability goes I think that the best solution is to
split the test into two, one for possitive cases and one (or a few more)
for negative ones...

-- 
Cyril Hrubis
chrubis@suse.cz

      reply	other threads:[~2017-01-23 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-19 15:36 [LTP] [PATCH v5 1/1] syscalls/mq_open: fix old tests + convert to use new API Petr Vorel
2017-01-23 16:07 ` Cyril Hrubis [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=20170123160750.GH25788@rei.lan \
    --to=chrubis@suse.cz \
    --cc=ltp@lists.linux.it \
    /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