public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: dwalker@fifo99.com
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Test Anything Protocal output
Date: Mon, 31 Aug 2015 12:22:44 +0200	[thread overview]
Message-ID: <20150831102243.GA17387@rei.suse.cz> (raw)
In-Reply-To: <20150829232628.GA14374@fifo99.com>

Hi!
> I read your January 2015 article where someone asked if TAP test output would be supported. It sounded like
> you were going to look into it. Did you make any progress?

Unfortunately not yet.

> The reason I asked if because I was wanting the same feature and I was going to review the LTP code to see
> how hard it would be to add it, but I wouldn't want to start if someone else has already done it. I did
> see anything in the git history tho.

Well, have a look at lib/tst_res.c, that is the place where test results
are stored/printed. Unfortunately this code hasn't been cleaned up yet.

I've started to work on this just recently. Just now I'm experimenting
with rewriting it from scratch keeping most of the API unchanged (since
we cannot change easily the API for > ~1000 testcases).

Then there is another problem, so far LTP testcases are executed using
the ltp-pan test driver, which executes testcases, catches segfaults,
etc. We would have to consider how that would interact with the output
generated from testcases.

One option would be to get rid of most of the pan functionality by
moving the test driver code into the test library, so that each testcase
would fork first, then run the real test in it's own virtual terminal,
etc.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

       reply	other threads:[~2015-08-31 10:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150829232628.GA14374@fifo99.com>
2015-08-31 10:22 ` Cyril Hrubis [this message]
     [not found]   ` <20150831170112.GA18725@fifo99.com>
2015-09-01 15:42     ` [LTP] Test Anything Protocal output Cyril Hrubis
     [not found]       ` <20150901232815.GA21660@fifo99.com>
2015-09-02 11:12         ` Cyril Hrubis

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=20150831102243.GA17387@rei.suse.cz \
    --to=chrubis@suse.cz \
    --cc=dwalker@fifo99.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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