selftests: question about git repos containing selftest.

selftests: question about git repos containing selftest.

[Young, David]

Greetings,

I'm trying out the new kernel selftests and was looking for the "bleeding edge" repository to clone.  According to the wiki https://kselftest.wiki.kernel.org/ this is the appropriate repo:
git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git

However, I am finding newer and more frequent changes are in linux-next.
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

Which should I clone for the most fresh changes?

-David Young

Re: selftests: question about git repos containing selftest.

[Greg KH]

On Tue, Dec 09, 2014 at 02:22:42PM -0500, Young, David wrote:
> Greetings,
> 
> I'm trying out the new kernel selftests and was looking for the "bleeding edge" repository to clone.  According to the wiki https://kselftest.wiki.kernel.org/ this is the appropriate repo:
> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
> 
> However, I am finding newer and more frequent changes are in linux-next.
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> 
> Which should I clone for the most fresh changes?

Are you sure you are looking at the correct branch for that git repo?
Which one were you using?

thanks,

greg k-h

Re: selftests: question about git repos containing selftest.

[Shuah Khan]

On Tue, Dec 9, 2014 at 12:46 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Tue, Dec 09, 2014 at 02:22:42PM -0500, Young, David wrote:
>> Greetings,
>>
>> I'm trying out the new kernel selftests and was looking for the "bleeding edge" repository to clone.  According to the wiki https://kselftest.wiki.kernel.org/ this is the appropriate repo:
>> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git
>>
>> However, I am finding newer and more frequent changes are in linux-next.
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>
>> Which should I clone for the most fresh changes?
>
> Are you sure you are looking at the correct branch for that git repo?
> Which one were you using?
>

Please find the patches slated for 3.19--rc1 in fixes branch. These
are the ones that
get pulled into linux-next for integration testing.

-- Shuah

RE: selftests: question about git repos containing selftest.

[Young, David]

Thanks, I was definitely looking at the master branch of linux-kselftest.

There are still more changes in linux-next repo, should those be considered as "in progress"?

-dave

-----Original Message-----
From: Shuah Khan [mailto:shuahkhan@gmail.com] 
Sent: Tuesday, December 09, 2014 3:21 PM
To: Greg KH
Cc: Young, David; linux-api@vger.kernel.org; shuahkh@osg.samsung.com; linux-kernel@vger.kernel.org
Subject: Re: selftests: question about git repos containing selftest.

On Tue, Dec 9, 2014 at 12:46 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Tue, Dec 09, 2014 at 02:22:42PM -0500, Young, David wrote:
>> Greetings,
>>
>> I'm trying out the new kernel selftests and was looking for the "bleeding edge" repository to clone.  According to the wiki https://kselftest.wiki.kernel.org/ this is the appropriate repo:
>> git://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.g
>> it
>>
>> However, I am finding newer and more frequent changes are in linux-next.
>> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>
>> Which should I clone for the most fresh changes?
>
> Are you sure you are looking at the correct branch for that git repo?
> Which one were you using?
>

Please find the patches slated for 3.19--rc1 in fixes branch. These are the ones that get pulled into linux-next for integration testing.

-- Shuah

Re: selftests: question about git repos containing selftest.

[Shuah Khan]

On Tue, Dec 9, 2014 at 1:25 PM, Young, David <dayoung-JqFfY2XvxFXQT0dZR+AlfA@public.gmane.org> wrote:
> Thanks, I was definitely looking at the master branch of linux-kselftest.
>
> There are still more changes in linux-next repo, should those be considered as "in progress"?
>

Patches in linux-kselftest fixes branch are the ones I included in my
pull request
I just sent out. linux-next might have some selftest patches that are part of a
series that depend on a sub-system API. Maybe that is what you are seeing
in linux-next.

For example there are ftrace selftest patches in linux-next that
depend on ftrace
sub-system, hence they funnel through ftrace. Same thing happens with mm
related things.

Do you have specific patches in linux-next that you have questions about?

-- Shuah

Re: selftests: question about git repos containing selftest.

[Davidlohr Bueso]

On Tue, 2014-12-09 at 13:34 -0700, Shuah Khan wrote:
> On Tue, Dec 9, 2014 at 1:25 PM, Young, David <dayoung@akamai.com> wrote:
> > Thanks, I was definitely looking at the master branch of linux-kselftest.
> >
> > There are still more changes in linux-next repo, should those be considered as "in progress"?
> >
> 
> Patches in linux-kselftest fixes branch are the ones I included in my
> pull request
> I just sent out. linux-next might have some selftest patches that are part of a
> series that depend on a sub-system API. Maybe that is what you are seeing
> in linux-next.

Is there any reason why Andrew isn't handling kselftests? Considering it
spans multiple subsystems, it seems far more appropriate that way.

RE: selftests: question about git repos containing selftest.

[Young, David]

> Do you have specific patches in linux-next that you have questions about?

Mostly I am interested in executing kselftests via something like autotest or Hudson/jenkins as a quick smoketest.  I understand it's still very much an in-progress feature, but would like the closest thing to a stable set of tests to regularly clone and use.  I suppose I could just wait for whatever makes it into mainline, but I'm interested in seeing the planned test coverage and test output so that I can write appropriate "glue" for use with a continuous-integration test system.

-dave

Re: selftests: question about git repos containing selftest.

[Shuah Khan]

On Tue, Dec 9, 2014 at 2:08 PM, Young, David <dayoung@akamai.com> wrote:
>
>> Do you have specific patches in linux-next that you have questions about?
>
> Mostly I am interested in executing kselftests via something like autotest or Hudson/jenkins as a quick smoketest.  I understand it's still very much an in-progress feature, but would like the closest thing to a stable set of tests to regularly clone and use.  I suppose I could just wait for whatever makes it into mainline, but I'm interested in seeing the planned test coverage and test output so that I can write appropriate "glue" for use with a continuous-integration test system.
>

David,

Please follow fixes branch for patches that are going to be in the next mainline
release. I am planning to create devel or experimental branch to make my next
revision install target patches available for early testing for people
that want to
play with work in progress. Hope this is helpful.

thanks,
-- Shuah

RE: selftests: question about git repos containing selftest.

[Young, David]

Thanks for clearing this up, very helpful!

-dave

-----Original Message-----
From: Shuah Khan [mailto:shuahkhan@gmail.com] 
Sent: Tuesday, December 09, 2014 4:27 PM
To: Young, David
Cc: Greg KH; linux-api@vger.kernel.org; shuahkh@osg.samsung.com; linux-kernel@vger.kernel.org
Subject: Re: selftests: question about git repos containing selftest.

On Tue, Dec 9, 2014 at 2:08 PM, Young, David <dayoung@akamai.com> wrote:
>
>> Do you have specific patches in linux-next that you have questions about?
>
> Mostly I am interested in executing kselftests via something like autotest or Hudson/jenkins as a quick smoketest.  I understand it's still very much an in-progress feature, but would like the closest thing to a stable set of tests to regularly clone and use.  I suppose I could just wait for whatever makes it into mainline, but I'm interested in seeing the planned test coverage and test output so that I can write appropriate "glue" for use with a continuous-integration test system.
>

David,

Please follow fixes branch for patches that are going to be in the next mainline release. I am planning to create devel or experimental branch to make my next revision install target patches available for early testing for people that want to play with work in progress. Hope this is helpful.

thanks,
-- Shuah