The Linux Test Project has been released for JANUARY 2015
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 [email protected].
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 22 lines · Cyril Hrubis
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
Quoted 8 lines
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/
Hi,
congrats to the new release!
I will check my "iniza" setup of Linux v3.19-rc5 the "(runltp-)lite" way.
Can you please add checksum files (md5sum, sha256, etc.) to the place where we get the tarballs, please?
Thanks.
Regards,
- Sedat -
Quoted 29 lines
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/BuildSystemPatches, new tests, bugs, comments or questions should go to to our mailing list at [email protected].
--
Cyril Hrubis
[email protected]------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
Hi!
Quoted 6 lines
congrats to the new release!
I will check my "iniza" setup of Linux v3.19-rc5 the "(runltp-)lite" way.
Can you please add checksum files (md5sum, sha256, etc.) to the place where we get the tarballs, please?
These are provided by sf.net, if you browse the files on sf.net there is small circle with i on the right, that, when clicked on shows md5 and sha1. These were generated by sf.net servers but I've checked that they match the files I've created.
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 5 lines · Cyril Hrubis
Hi!
Quoted 4 lines
congrats to the new release!
I will check my "iniza" setup of Linux v3.19-rc5 the "(runltp-)lite" way.
Quoted 8 lines
Quoted 2 lines
Can you please add checksum files (md5sum, sha256, etc.) to the place where we get the tarballs, please?
These are provided by sf.net, if you browse the files on sf.net there is small circle with i on the right, that, when clicked on shows md5 and sha1. These were generated by sf.net servers but I've checked that they match the files I've created.
Thanks, you are right.
I couldn't see that "little i" with my "eyes" :-).
- Sedat -
On Mon, Jan 19, 2015 at 4:28 PM, Sedat Dilek <[email protected]> wrote:
[...]
Quoted 3 lines
I will check my "iniza" setup of Linux v3.19-rc5 the "(runltp-)lite" way.
Attached are the runltp-lite result and my kernel-config.
I see a lot of "unexpected" failures, can you comment on them?
Thanks.
- Sedat -
Hi!
Quoted 6 lines
Quoted 2 lines
I will check my "iniza" setup of Linux v3.19-rc5 the "(runltp-)lite" way.
Attached are the runltp-lite result and my kernel-config.
I see a lot of "unexpected" failures, can you comment on them?
Most of the failures comes from EBUSY while trying to umount filesystems. Do you have gvfsd-trash running? That thing is known to probe newly mounted filesystems preventing them from being unmounted for a certain amount of time.
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 4 lines · Cyril Hrubis
Hi!
Quoted 3 lines
Quoted 2 lines
I will check my "iniza" setup of Linux v3.19-rc5 the "(runltp-)lite" way.
Quoted 9 lines
Quoted 3 lines
Attached are the runltp-lite result and my kernel-config.
I see a lot of "unexpected" failures, can you comment on them?
Most of the failures comes from EBUSY while trying to umount filesystems. Do you have gvfsd-trash running? That thing is known to probe newly mounted filesystems preventing them from being unmounted for a certain amount of time.
Yupp, that popped up.
How can I disable that gvfsd (here: Ubuntu/precise? And can this issue be documented?
- Sedat -
Hi!
Quoted 8 lines
Quoted 5 lines
Most of the failures comes from EBUSY while trying to umount filesystems. Do you have gvfsd-trash running? That thing is known to probe newly mounted filesystems preventing them from being unmounted for a certain amount of time.
Yupp, that popped up.
How can I disable that gvfsd (here: Ubuntu/precise?
Just kill the process, or run the testcases via ssh session.
Quoted 1 line
And can this issue be documented?
Hmm, maybe we can change the test cases to complain loudly if the process is found running.
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 10 lines · Cyril Hrubis
Hi!
Quoted 8 lines
Quoted 5 lines
Most of the failures comes from EBUSY while trying to umount filesystems. Do you have gvfsd-trash running? That thing is known to probe newly mounted filesystems preventing them from being unmounted for a certain amount of time.
Yupp, that popped up.
How can I disable that gvfsd (here: Ubuntu/precise?
Quoted 7 lines
Just kill the process, or run the testcases via ssh session.
Quoted 1 line
And can this issue be documented?
Hmm, maybe we can change the test cases to complain loudly if the process is found running.
Good idea.
- Sedat -
Hi!
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Yupp, that popped up.
How can I disable that gvfsd (here: Ubuntu/precise?Just kill the process, or run the testcases via ssh session.
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
And can this issue be documented?
Hmm, maybe we can change the test cases to complain loudly if the process is found running.
Good idea.
And should be fixed in latest git. Now the testcases complain about the failure, give a hint what may be causing it, and if the umount() is not the the syscall under test, it's retried a few times with short usleep between.
Signature · 2 lines
Cyril Hrubis [email protected]
Quoted 12 lines · Cyril Hrubis
Hi!
Quoted 11 lines
Quoted 10 lines
Quoted 2 lines
Yupp, that popped up.
How can I disable that gvfsd (here: Ubuntu/precise?Just kill the process, or run the testcases via ssh session.
Quoted 1 line
And can this issue be documented?
Hmm, maybe we can change the test cases to complain loudly if the process is found running.
Quoted 7 lines
Quoted 1 line
Good idea.
And should be fixed in latest git. Now the testcases complain about the failure, give a hint what may be causing it, and if the
umount()is not the the syscall under test, it's retried a few times with short usleep between.
Thanks for fixing this!
For followers, here the fix [1]...
commit 10b61174ce0019833cc4c2e95ddbeec723131920 "syscalls: umount01: Give a hint on failure with EBUSY"
For the sake of completeness (here: Ubuntu/precise)...
# ps axu | grep v[f]s wearefam 2006 0.0 0.1 54068 5044 ? S 08:55 0:00 /usr/lib/gvfs/gvfsd wearefam 2008 0.0 0.1 207920 5656 ? Sl 08:55 0:00 /usr/lib/gvfs//gvfs-fuse-daemon -f /home/wearefam/.gvfs wearefam 2056 0.0 0.1 72228 7224 ? S 08:56 0:00 /usr/lib/gvfs/gvfs-gdu-volume-monitor wearefam 2070 0.0 0.0 143600 3788 ? Sl 08:56 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor wearefam 2075 0.0 0.1 61852 5440 ? S 08:56 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor wearefam 2087 0.0 0.1 58684 6372 ? S 08:56 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.6 /org/gtk/gvfs/exec_spaw/0 wearefam 2089 0.0 0.1 54068 5472 ? S 08:56 0:00 /usr/lib/gvfs/gvfsd-burn --spawner :1.6 /org/gtk/gvfs/exec_spaw/1
( Indeed it's a "gvfsd-trash" instance running :-). )
- Sedat -
[1] https://github.com/linux-test-project/ltp/commit/10b61174ce0019833cc4c2e95ddbeec723131920