Date: Tue, 25 May 2010 11:41:25 +0400 From: Andrey Ponomarenko <susanin@ispras.ru> To: Garrett Cooper <yanefbsd@gmail.com> Cc: ports@freebsd.org Subject: Re: new upstream tracker (linuxtesting.org) Message-ID: <4BFB7F25.2030205@ispras.ru> In-Reply-To: <AANLkTikxaIA6QvHAkw5HtAY81nQzlJzcB008HfMR0mny@mail.gmail.com> References: <4BF7C5EC.20500@ispras.ru> <AANLkTikxaIA6QvHAkw5HtAY81nQzlJzcB008HfMR0mny@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/22/2010 11:30 PM, Garrett Cooper wrote: > On Sat, May 22, 2010 at 4:54 AM, Andrey Ponomarenko <susanin@ispras.ru> wrote: > >> Hello, I'm from ISPRAS and we have created an experimental system for >> monitoring and analyzing of upstream libraries development. It may be >> helpful for analyzing risks of updating one of the distribution >> components (shared libraries). The web page of upstream-tracker is: >> http://linuxtesting.org/upstream-tracker/ >> It now includes ABI changes analysis and API shallow test results for >> several versions of 60 popular open source libraries. >> Any bugs or feature requests are welcome. Thanks. >> > Just out of curiosity, is this a system for monitoring the 3rd > party libraries that have been imported into our base system, Yes, you are right > or is it > a generic tool for running testcases? No > I'll poke at it further, in the > meantime, but it would be helpful if an expert could comment on the > issue more :). > I ask because Linux in and of itself doesn't really have a base > system and everything's packages from the get-go, whereas *BSD has a > userland with some 3rd party packages all wrapped into one base > system. > Also, how do you `test' the applications -- using the runtime > tests produced in previous versions, Did you mean a regression tests? We do not run such tests now but have some plans on the future, because it is a very significant aspect of testing. > or by just executing applications > and observing whether or not the API calls pass or fail? > Yes, we just run many test cases (one test case for one particular interface) and searching for segmentation faults and other serious problems in the library API. All test cases are automatically generated straight from the library header files (so-called "header-driven" approach). Also we perform checks for ABI breakages in the sequential versions of the library. > Thanks! > -Garrett > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > -- Andrey Ponomarenko Linux Verification Center, ISPRAS web: http://www.linuxtesting.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BFB7F25.2030205>