public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Cyril Hrubis <chrubis@suse.cz>
To: ltp-list@lists.sourceforge.net, linux-kernel@vger.kernel.org,
	libc-alpha@sourceware.org
Cc: lwn@lwn.net, akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: [LTP] The Linux Test Project has been released for JANUARY 2015
Date: Mon, 19 Jan 2015 13:23:10 +0100	[thread overview]
Message-ID: <20150119122310.GA27065@rei> (raw)

God news everyone,

the Linux Test Project test suite stable release for *January 2015* has
been released.

Since the last release 139 patches by 21 authors were merged.

Notable changes are:

* Fixes and enhancements of network testcases by Alexey Kodanev

* New testcases for mount, network and ipc namespaces by Matus Marhefka

* New testcase for fanotify ignore masks

* New policy and library helpers to install and access testcase datafailes

* Use of coccinelle and spatch to fix bugs and cleanup old code

* And many more smaller fixes and enhancements


If you are not familiar with LTP there is a nice article at LWN.net
https://lwn.net/Articles/625969/.

The latest version of the test-suite contains 3000+ tests for the Linux
and can be downloaded at:

http://sourceforge.net/projects/ltp/files/LTP%20Source/ltp-20150119/

The project pages as well as GIT repository are hosted on GitHub for
quite some time now:

https://github.com/linux-test-project/ltp
http://linux-test-project.github.io/

If you ever wondered how to write a LTP testcase, don't miss our developer
documentation at:

https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines
https://github.com/linux-test-project/ltp/wiki/BuildSystem

Patches, new tests, bugs, comments or questions should go to
to our mailing list at ltp-list@lists.sourceforge.net.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2015-01-19 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 12:23 Cyril Hrubis [this message]
     [not found] ` <CA+icZUV53AWik-bS4a3DwgExD26nhCWxJWb-kGN_nAOWsikuLA@mail.gmail.com>
2015-01-19 16:03   ` [LTP] The Linux Test Project has been released for JANUARY 2015 Cyril Hrubis
     [not found]   ` <CA+icZUVSnYv3-rh6sBr8vgDsc80Qnr3yK_OZ6AezVHPrDcKXbg@mail.gmail.com>
2015-01-20 11:56     ` Cyril Hrubis
     [not found]       ` <CA+icZUW3=TkMvEzs3DXZYt0BC5JjUtXiCsVSt3ikHwxPyzu3=A@mail.gmail.com>
2015-01-20 13:28         ` Cyril Hrubis
     [not found]           ` <CA+icZUV13kXzOBnf0Ck9_0UwJPSvKziOoy8_4jORQMzMvWC9LQ@mail.gmail.com>
2015-01-29 15:55             ` 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=20150119122310.GA27065@rei \
    --to=chrubis@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=lwn@lwn.net \
    --cc=torvalds@linux-foundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox