Sorry, centos-6 build, not Fedora:
https://ci.bigtop.apache.org/job/Bigtop-trunk-select-from-branch/OS=centos-6/21/console

On Wed, Aug 2, 2017 at 6:50 PM, Konstantin Shvachko <shv.had...@gmail.com>
wrote:

> Hey Cos,
>
> Looked at Fedora 6 build failure in the final Bigtop packaging stage:
>
> + tar --strip-components=1 -xzvf 
> ../hadoop-dist/target/hadoop-2.7.4-SNAPSHOT.tar.gz
> tar (child): ../hadoop-dist/target/hadoop-2.7.4-SNAPSHOT.tar.gz: Cannot open: 
> No such file or directory
>
> Is it because of the "-SNAPSHOT" thing? Now that branch-2.7.4's version is 
> simply "2.7.4".
>
> Thanks,
>
> --Konst
>
>
>
> On Wed, Aug 2, 2017 at 5:41 PM, Konstantin Boudnik <c...@apache.org> wrote:
>
>> I have re-built Hadoop from the latest RC on branch-2.7.4 [1]
>> CentOS6 build has failed for some weird reason (7 is ok), but who
>> cares about this old-crap really ;)
>>
>> [1] https://ci.bigtop.apache.org/job/Bigtop-trunk-select-from-branch/21/
>> --
>>   With regards,
>> Konstantin (Cos) Boudnik
>> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>>
>> Disclaimer: Opinions expressed in this email are those of the author,
>> and do not necessarily represent the views of any company the author
>> might be affiliated with at the moment of writing.
>>
>>
>> On Fri, Jul 21, 2017 at 11:33 PM, Konstantin Shvachko
>> <shv.had...@gmail.com> wrote:
>> > Appreciate this, Cos.
>> >
>> > On Fri, Jul 21, 2017 at 9:26 PM, Konstantin Boudnik <c...@apache.org>
>> wrote:
>> >
>> >> Just to wrap up this issue: 2.7.4 artifacts are being built by out
>> >> Jenkins out of BIGTOP-2839 branch.
>> >> The packages are available from the latest build. I will try to spin
>> >> up some testing over the weekend to have some reasonable reassurance
>> >> it is good enough to be included.
>> >>
>> >> Thanks,
>> >>   Cos
>> >> --
>> >>   With regards,
>> >> Konstantin (Cos) Boudnik
>> >> 2CAC 8312 4870 D885 8616  6115 220F 6980 1F27 E622
>> >>
>> >> Disclaimer: Opinions expressed in this email are those of the author,
>> >> and do not necessarily represent the views of any company the author
>> >> might be affiliated with at the moment of writing.
>> >>
>> >>
>> >> On Fri, Jul 14, 2017 at 7:26 PM, Konstantin Boudnik <c...@apache.org>
>> >> wrote:
>> >> > Well, I am a bit at a pickle here.
>> >> >
>> >> > - the git build is broken and it's unclear why (I opened
>> BIGTOP-2847 to
>> >> track)
>> >> > - no biggy, because I simply can download the zip file right of the
>> >> Github
>> >> >   branch using [1]. Well, turns out there's an issue with 'expires'
>> >> attribute
>> >> >   in the cookie and the zip file cannot be downloaded, failing with
>> the
>> >> >   following error message
>> >> >
>> >> > Executing task ':hadoop-download' (up-to-date check took 0.001 secs)
>> due
>> >> to:
>> >> >   Task has not declared any outputs.
>> >> > Invalid cookie header: "Set-Cookie: logged_in=no; domain=.github.com
>> ;
>> >> path=/; expires=Wed, 15 Jul 2037 02:22:41 -0000; secure; HttpOnly".
>> Invalid
>> >> 'expires' attribute: Wed, 15 Jul 2037 02:22:41 -0000
>> >> >
>> >> >
>> >> > At this point I am at lost and I don't know how to proceed ;( Let me
>> >> think about this for a moment.
>> >> >
>> >> > [1] https://github.com/apache/hadoop/archive/branch-2.7.zip
>> >> >
>> >> > Cos
>> >> >
>> >> > On Fri, Jul 14, 2017 at 04:42AM, Evans Ye wrote:
>> >> >> Cos,
>> >> >>
>> >> >> Can we build from git?
>> >> >> Last time i tried and it doea not work.
>> >> >> Would be great if you xan light me up a bit.
>> >> >>
>> >> >> MrAsanjar . <afsan...@gmail.com>於 2017年7月14日 週五,上午10:38寫道:
>> >> >>
>> >> >> > where is source for hadoop 2.7.4? can't find it in github.
>> >> >> > need it to verify JIRA https://issues.apache.org/
>> >> jira/browse/HADOOP-13579
>> >> >> >
>> >> >> > On Thu, Jul 13, 2017 at 7:52 PM, Konstantin Boudnik <
>> c...@apache.org>
>> >> >> > wrote:
>> >> >> >
>> >> >> > > On Thu, Jul 13, 2017 at 05:50PM, Konstantin Boudnik wrote:
>> >> >> > > > Certainly having an official release is much preferable.
>> However,
>> >> we
>> >> >> > can
>> >> >> > > try
>> >> >> > > > to go with a branch for now. Say, I can change the patch to
>> start
>> >> >> > > building
>> >> >> > > > from the git instead, so we can start testing it on a separate
>> >> branch
>> >> >> > > for now.
>> >> >> > >
>> >> >> > > Is there at least a branch where the work is being done? I
>> don't see
>> >> >> > 2.7.4
>> >> >> > > in
>> >> >> > > the github. Please advise.
>> >> >> > >
>> >> >> > > > Once the release is ready (and if 1.2.1 is still unreleased on
>> >> our end)
>> >> >> > > we'll
>> >> >> > > > move to the official bits.
>> >> >> > > >
>> >> >> > > > Cos
>> >> >> > > >
>> >> >> > > > On Thu, Jul 13, 2017 at 05:33PM, Konstantin Shvachko wrote:
>> >> >> > > > > Thank you, Evans. Would be really good to include 2.7.4.
>> >> >> > > > > Do you guys need the actual Hadoop release for inclusion
>> into a
>> >> >> > BigTop
>> >> >> > > > > release?
>> >> >> > > > >
>> >> >> > > > > Thanks,
>> >> >> > > > > --Konst
>> >> >> > > > >
>> >> >> > > > > On Wed, Jul 12, 2017 at 10:52 PM, Evans Ye <
>> evan...@apache.org>
>> >> >> > wrote:
>> >> >> > > > >
>> >> >> > > > > > I'm actually OK to have 2.7.4 included in 1.2.1, if that's
>> >> ready in
>> >> >> > > master.
>> >> >> > > > > > Right now 1.2.1 release is blocked by building up a build
>> >> slave
>> >> >> > > docker
>> >> >> > > > > > image for SuSE 42.1.
>> >> >> > > > > > Once the obstacle removed. The release process will
>> proceed.
>> >> >> > > > > > If 2.7.4 is ready then, we can try to include it.
>> >> >> > > > > >
>> >> >> > > > > >
>> >> >> > > > > > 2017-07-13 8:55 GMT+08:00 Konstantin Boudnik <
>> c...@apache.org
>> >> >:
>> >> >> > > > > >
>> >> >> > > > > > > Oh, one more question: is there a JIRA ticket tracking
>> 2.7.4
>> >> >> > > release? I
>> >> >> > > > > > > couldn't find it somehow. Thanks
>> >> >> > > > > > >
>> >> >> > > > > > > Cos
>> >> >> > > > > > >
>> >> >> > > > > > > On Wed, Jul 12, 2017 at 05:45PM, Konstantin Boudnik
>> wrote:
>> >> >> > > > > > > > Thanks Konstantin!
>> >> >> > > > > > > >
>> >> >> > > > > > > > I would venture the guess it includes mostly bug
>> fixes and
>> >> >> > > perhaps some
>> >> >> > > > > > > > minor performance improvements? I guess as such it
>> won't
>> >> be
>> >> >> > that
>> >> >> > > much
>> >> >> > > > > > > > different from 2.7.3 we currently support. At least
>> from
>> >> the
>> >> >> > > APIs and
>> >> >> > > > > > UX
>> >> >> > > > > > > point
>> >> >> > > > > > > > of view. Now, a few weeks might be an over-stretch
>> (what
>> >> is it
>> >> >> > > by your
>> >> >> > > > > > > > estimation?) and we might not be willing to hold
>> current
>> >> >> > release
>> >> >> > > that
>> >> >> > > > > > > long,
>> >> >> > > > > > > > but this would RM's call (hey Evans!),
>> >> >> > > > > > > >
>> >> >> > > > > > > > Adding this to the master (presumably for 1.3 or even
>> >> 1.2.2) is
>> >> >> > > easy
>> >> >> > > > > > > though
>> >> >> > > > > > > > and should be done so we can upgrade the stack to the
>> >> latest
>> >> >> > > 2.7.x line
>> >> >> > > > > > > until
>> >> >> > > > > > > > 2.8 (or whatever would be the next one) line is mature
>> >> enough.
>> >> >> > > At any
>> >> >> > > > > > > rate, I
>> >> >> > > > > > > > have created BIGTOP-2839 to track this.
>> >> >> > > > > > > >
>> >> >> > > > > > > > Thoughts?
>> >> >> > > > > > > >   Cos
>> >> >> > > > > > > >
>> >> >> > > > > > > > On Wed, Jul 12, 2017 at 01:17PM, Konstantin Shvachko
>> >> wrote:
>> >> >> > > > > > > > > Hi guys,
>> >> >> > > > > > > > >
>> >> >> > > > > > > > > We plan to release Hadoop 2.7.4 in the next few
>> weeks.
>> >> >> > > > > > > > > I was wondering if you could include it into Bigtop.
>> >> >> > > > > > > > > It would be really valuable to add Bigtop testing
>> for
>> >> the
>> >> >> > > release.
>> >> >> > > > > > > > > I believe you already have support for earlier
>> Hadoop
>> >> 2.7
>> >> >> > > release.
>> >> >> > > > > > > > > Hope it wouldn't be too much trouble to integrate
>> 2.7.4.
>> >> >> > > > > > > > >
>> >> >> > > > > > > > > Thanks,
>> >> >> > > > > > > > > --Konst
>> >> >> > > > > > >
>> >> >> > > > > > >
>> >> >> > > > > > >
>> >> >> > > > > >
>> >> >> > >
>> >> >> > >
>> >> >> > >
>> >> >> >
>> >>
>>
>
>

Reply via email to