Fwd: if ceph tracker says the source was QA, what version that I have to checkout?

Fwd: if ceph tracker says the source was QA, what version that I have to checkout?

[agung Laksono]

[-- Attachment #1.1: Type: text/plain, Size: 524 bytes --]

Hi All ceph users,

I am interesting to learn ceph bug.

Some bugs that I learned pointing particular ceph version or tags for their
buggy part.
However I found some bugs put Q/A as the source.
For instance http://tracker.ceph.com/issues/9301

when I checked out on giant and firefly version, I saw the significant
different between
the version and the revision that changed by the developer.

My question is how to have a buggy version( version when the patch has not
been implemented)?

Thanks

-- 
Cheers,

Agung Laksono

[-- Attachment #1.2: Type: text/html, Size: 1102 bytes --]

[-- Attachment #2: Type: text/plain, Size: 178 bytes --]

_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] Fwd: if ceph tracker says the source was QA, what version that I have to checkout?

[Brad Hubbard]

On Mon, Oct 10, 2016 at 9:21 AM, agung Laksono <agung.smarts@gmail.com> wrote:
>
> Hi All ceph users,
>
> I am interesting to learn ceph bug.
>
> Some bugs that I learned pointing particular ceph version or tags for their
> buggy part.
> However I found some bugs put Q/A as the source.
> For instance http://tracker.ceph.com/issues/9301
>
> when I checked out on giant and firefly version, I saw the significant
> different between
> the version and the revision that changed by the developer.
>
> My question is how to have a buggy version( version when the patch has not
> been implemented)?

For this particular commit we can ask git.

http://tracker.ceph.com/projects/ceph/repository/revisions/c421b55e8e15ef04ca8aeb47f7d090375eaa8573

$ git describe c421b55e8e15ef04ca8aeb47f7d090375eaa8573
v0.85-884-gc421b55

So this was the 884th commit after the v0.85 tag and you need to check
out a copy of the source before that.

>
> Thanks
>
> --
> Cheers,
>
> Agung Laksono
>
> _______________________________________________
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>



-- 
Cheers,
Brad

Re: Fwd: if ceph tracker says the source was QA, what version that I have to checkout?

[agung Laksono]

[-- Attachment #1.1: Type: text/plain, Size: 1660 bytes --]

thank you for the answer Brad,

so the thing that I have to do is that:
- see the commit version
- checkout to the commit version
- see the log ( git log -p -1)
- ultimately, checkout the older one.

Am I correct?


On Mon, Oct 10, 2016 at 6:28 AM, Brad Hubbard <bhubbard-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:

> On Mon, Oct 10, 2016 at 9:21 AM, agung Laksono <agung.smarts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
> >
> > Hi All ceph users,
> >
> > I am interesting to learn ceph bug.
> >
> > Some bugs that I learned pointing particular ceph version or tags for
> their
> > buggy part.
> > However I found some bugs put Q/A as the source.
> > For instance http://tracker.ceph.com/issues/9301
> >
> > when I checked out on giant and firefly version, I saw the significant
> > different between
> > the version and the revision that changed by the developer.
> >
> > My question is how to have a buggy version( version when the patch has
> not
> > been implemented)?
>
> For this particular commit we can ask git.
>
> http://tracker.ceph.com/projects/ceph/repository/revisions/
> c421b55e8e15ef04ca8aeb47f7d090375eaa8573
>
> $ git describe c421b55e8e15ef04ca8aeb47f7d090375eaa8573
> v0.85-884-gc421b55
>
> So this was the 884th commit after the v0.85 tag and you need to check
> out a copy of the source before that.
>
> >
> > Thanks
> >
> > --
> > Cheers,
> >
> > Agung Laksono
> >
> > _______________________________________________
> > ceph-users mailing list
> > ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >
>
>
>
> --
> Cheers,
> Brad
>



-- 
Cheers,

Agung Laksono

[-- Attachment #1.2: Type: text/html, Size: 3120 bytes --]

[-- Attachment #2: Type: text/plain, Size: 178 bytes --]

_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: Fwd: if ceph tracker says the source was QA, what version that I have to checkout?

[Brad Hubbard]

On Mon, Oct 10, 2016 at 9:51 AM, agung Laksono <agung.smarts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> thank you for the answer Brad,
>
> so the thing that I have to do is that:
> - see the commit version
> - checkout to the commit version
> - see the log ( git log -p -1)
> - ultimately, checkout the older one.
>
> Am I correct?

Yes, that's pretty much it. The following should be your starting point.

$ git checkout c421b55e8e15ef04ca8aeb47f7d090375eaa8573~1

It's not guaranteed that every commit will build and test successfully so you
may need to move further back from that point or even use the previous tag (in
this case v0.85).

>
>
> On Mon, Oct 10, 2016 at 6:28 AM, Brad Hubbard <bhubbard-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>>
>> On Mon, Oct 10, 2016 at 9:21 AM, agung Laksono <agung.smarts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> wrote:
>> >
>> > Hi All ceph users,
>> >
>> > I am interesting to learn ceph bug.
>> >
>> > Some bugs that I learned pointing particular ceph version or tags for
>> > their
>> > buggy part.
>> > However I found some bugs put Q/A as the source.
>> > For instance http://tracker.ceph.com/issues/9301
>> >
>> > when I checked out on giant and firefly version, I saw the significant
>> > different between
>> > the version and the revision that changed by the developer.
>> >
>> > My question is how to have a buggy version( version when the patch has
>> > not
>> > been implemented)?
>>
>> For this particular commit we can ask git.
>>
>>
>> http://tracker.ceph.com/projects/ceph/repository/revisions/c421b55e8e15ef04ca8aeb47f7d090375eaa8573
>>
>> $ git describe c421b55e8e15ef04ca8aeb47f7d090375eaa8573
>> v0.85-884-gc421b55
>>
>> So this was the 884th commit after the v0.85 tag and you need to check
>> out a copy of the source before that.
>>
>> >
>> > Thanks
>> >
>> > --
>> > Cheers,
>> >
>> > Agung Laksono
>> >
>> > _______________________________________________
>> > ceph-users mailing list
>> > ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
>> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>> >
>>
>>
>>
>> --
>> Cheers,
>> Brad
>
>
>
>
> --
> Cheers,
>
> Agung Laksono
>



-- 
Cheers,
Brad

Re: Fwd: if ceph tracker says the source was QA, what version that I have to checkout?

[agung Laksono]

[-- Attachment #1.1: Type: text/plain, Size: 2680 bytes --]

Yes you're right.

Sometimes it tested not in a single step back then.
but it also possible to be tested some version steps in the previous
commits.

thanks for helping!


On Mon, Oct 10, 2016 at 7:18 AM, Brad Hubbard <bhubbard-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:

>
>
> On Mon, Oct 10, 2016 at 9:51 AM, agung Laksono <agung.smarts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> wrote:
> > thank you for the answer Brad,
> >
> > so the thing that I have to do is that:
> > - see the commit version
> > - checkout to the commit version
> > - see the log ( git log -p -1)
> > - ultimately, checkout the older one.
> >
> > Am I correct?
>
> Yes, that's pretty much it. The following should be your starting point.
>
> $ git checkout c421b55e8e15ef04ca8aeb47f7d090375eaa8573~1
>
> It's not guaranteed that every commit will build and test successfully so
> you
> may need to move further back from that point or even use the previous tag
> (in
> this case v0.85).
>
> >
> >
> > On Mon, Oct 10, 2016 at 6:28 AM, Brad Hubbard <bhubbard-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
> wrote:
> >>
> >> On Mon, Oct 10, 2016 at 9:21 AM, agung Laksono <agung.smarts-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
> >> wrote:
> >> >
> >> > Hi All ceph users,
> >> >
> >> > I am interesting to learn ceph bug.
> >> >
> >> > Some bugs that I learned pointing particular ceph version or tags for
> >> > their
> >> > buggy part.
> >> > However I found some bugs put Q/A as the source.
> >> > For instance http://tracker.ceph.com/issues/9301
> >> >
> >> > when I checked out on giant and firefly version, I saw the significant
> >> > different between
> >> > the version and the revision that changed by the developer.
> >> >
> >> > My question is how to have a buggy version( version when the patch has
> >> > not
> >> > been implemented)?
> >>
> >> For this particular commit we can ask git.
> >>
> >>
> >> http://tracker.ceph.com/projects/ceph/repository/revisions/
> c421b55e8e15ef04ca8aeb47f7d090375eaa8573
> >>
> >> $ git describe c421b55e8e15ef04ca8aeb47f7d090375eaa8573
> >> v0.85-884-gc421b55
> >>
> >> So this was the 884th commit after the v0.85 tag and you need to check
> >> out a copy of the source before that.
> >>
> >> >
> >> > Thanks
> >> >
> >> > --
> >> > Cheers,
> >> >
> >> > Agung Laksono
> >> >
> >> > _______________________________________________
> >> > ceph-users mailing list
> >> > ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
> >> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >> >
> >>
> >>
> >>
> >> --
> >> Cheers,
> >> Brad
> >
> >
> >
> >
> > --
> > Cheers,
> >
> > Agung Laksono
> >
>
>
>
> --
> Cheers,
> Brad
>



-- 
Cheers,

Agung Laksono

[-- Attachment #1.2: Type: text/html, Size: 4745 bytes --]

[-- Attachment #2: Type: text/plain, Size: 178 bytes --]

_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com