I also run check-all against Debian and build was successful, although I
saw a bunch of this error:

apache-samza-0.12.0-src/samza-hdfs/src/main/java/org/apache/samza/system/hdfs/HdfsSystemConsumer.java:59:
error: unmappable character for encoding ASCII
 *
 ?????????????????????????????????????????????????????????????????????????????

I don't think they are a blocker, it's some characters not being able to be
parsed when doing the scalaCompile task for the samza-hdfs component. Is it
worth opening a JIRA to fix this?


Best,

Renato M.


2017-02-13 22:20 GMT+01:00 Navina Ramesh <nram...@linkedin.com.invalid>:

> I ran check-all against Mac and integration tests on Linux. Looks good with
> no concerning issues.
>
> +1 (binding)
>
> Thanks!
> Navina
>
> On Fri, Feb 10, 2017 at 9:25 AM, Boris S <bor...@gmail.com> wrote:
>
> > I also successfully ran the integration tests on Linux. All passed.
> > +1 non-binding
> >
> > On Wed, Feb 8, 2017 at 4:57 PM, Jacob Maes <jacob.m...@gmail.com> wrote:
> >
> > > Build and integration tests were successful for me.
> > >
> > > +1 non-binding
> > >
> > > On Wed, Feb 8, 2017 at 4:48 PM, xinyu liu <xinyuliu...@gmail.com>
> wrote:
> > >
> > > > Ran build, checkAll and integration tests. All passed.
> > > >
> > > > +1 non-binding.
> > > >
> > > > Thanks,
> > > > Xinyu
> > > >
> > > > On Wed, Feb 8, 2017 at 4:18 PM, Boris S <bor...@gmail.com> wrote:
> > > >
> > > > > Cloned the release and ran build, test and checkAll.sh
> > > > > All passed.
> > > > > Verified MD5 and the signature.
> > > > > Got warning - "this key is not certified with a trusted
> signature". I
> > > > guess
> > > > > it is ok.
> > > > >
> > > > > +1
> > > > >
> > > > > On Mon, Feb 6, 2017 at 5:32 PM, Jagadish Venkatraman <
> > > > > jagadish1...@gmail.com
> > > > > > wrote:
> > > > >
> > > > > > This is a call for a vote on a release of Apache Samza 0.12.0.
> > Thanks
> > > > to
> > > > > > everyone who has contributed to this release. We are very glad to
> > see
> > > > > some
> > > > > > new contributors in this release.
> > > > > >
> > > > > > The release candidate can be downloaded from here:
> > > > > > http://home.apache.org/~jagadish/samza-0.12.0-rc2/
> > > > > >
> > > > > > The release candidate is signed with pgp key AF81FFBF, which can
> be
> > > > found
> > > > > > on keyservers:
> > > > > > http://pgp.mit.edu/pks/lookup?op=get&search=0xAF81FFBF
> > > > > >
> > > > > > The git tag is release-0.12.0-rc2 and signed with the same pgp
> key:
> > > > > > https://git-wip-us.apache.org/repos/asf?p=samza.git;a=tag;h=
> > > > > > refs/tags/release-0.12.0-rc2
> > > > > >
> > > > > > Test binaries have been published to Maven's staging repository,
> > and
> > > > are
> > > > > > available here:
> > > > > > https://repository.apache.org/content/repositories/
> > > orgapachesamza-1018
> > > > > >
> > > > > > Note that the binaries were built with JDK8 without incident.
> > > > > >
> > > > > > 26 issues were resolved for this release:
> > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20S
> > > > > > AMZA%20AND%20fixVersion%20in%20(0.12%2C%200.12.0)%20AND%20st
> > > > > > atus%20in%20(Resolved%2C%20Closed)
> > > > > >
> > > > > > The vote will be open for 72 hours (end in 6PM Thursday,
> 02/09/2017
> > > ).
> > > > > >
> > > > > > Please download the release candidate, check the
> hashes/signature,
> > > > build
> > > > > it
> > > > > > and test it, and then please vote:
> > > > > >
> > > > > >
> > > > > > [ ] +1 approve
> > > > > >
> > > > > > [ ] +0 no opinion
> > > > > >
> > > > > > [ ] -1 disapprove (and reason why)
> > > > > >
> > > > > >
> > > > > > +1 from my side for the release.
> > > > > >
> > > > > > Cheers!
> > > > > >
> > > > > > --
> > > > > > Jagadish V,
> > > > > > Graduate Student,
> > > > > > Department of Computer Science,
> > > > > > Stanford University
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
> --
> Navina R.
>

Reply via email to