+0 (1 Test is failing for me) * Sig Validated * Hashes Validated * Built on Ubuntu 14.04 [Used Ubuntu Package libleveldb1 & cmake 3.2 successfully: Linux edge1 4.4.0-75-generic #96~14.04.1-Ubuntu SMP Thu Apr 20 11:06:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux] * Running tests I hit a segfault, checking to see if its specific my environment or not. Working with Mark Parisi to identify root.
Test YAML Config 1 ------------------------------------------------------------------------------- /data/ssd01/builds/minifi-020/nifi-minifi-cpp-0.2.0-source/libminifi/test/unit/YamlCongifurationTests.cpp:28 ............................................................................... /data/ssd01/builds/minifi-020/nifi-minifi-cpp-0.2.0-source/libminifi/test/unit/YamlCongifurationTests.cpp:28: FAILED: due to a fatal error condition: SIGSEGV - Segmentation violation signal =============================================================================== test cases: 15 | 14 passed | 1 failed assertions: 39 | 38 passed | 1 failed On Sun, May 7, 2017 at 2:28 PM, Aldrin Piri <aldrinp...@gmail.com> wrote: > Looks like we have removed the problematic areas of the third party > inclusions, updated the README and updated the tarball generation to avoid > including generated doc files. I will being working on an RC2 based off of > commit hash fa913b4174e1c874ddb12e4901c48bd86a7f70e4. > > Thanks! > Aldrin > > On Sat, May 6, 2017 at 10:41 AM, Aldrin Piri <aldrinp...@gmail.com> wrote: > > > Yep, definitely seems like a good candidate to also include. Will review > > that as well and get incorporated if all looks good. Thanks for bringing > > to my attention. > > > > --aldrin > > > > On Sat, May 6, 2017 at 10:35 AM, Marc <phroc...@apache.org> wrote: > > > >> Aldrin, > >> I was preparing a response that we may wish to update the readme per > >> https://github.com/apache/nifi-minifi-cpp/pull/92 . We don't include > the > >> full list of processors. Since the list is small it would be useful to > >> keep > >> it up to date at the moment. In the future we can prepare some auto > >> documentation that we link to from the readme. > >> > >> > >> On Sat, May 6, 2017 at 9:55 AM, Aldrin Piri <ald...@apache.org> wrote: > >> > >> > All, > >> > > >> > After doing some review for the release process, it was seen that some > >> > artifacts of our third party dependencies had unknown origins making > it > >> > hard to determine the full scope of licensing concerns. To avoid any > >> > issues, I am cancelling this vote such that they can be removed. > >> > > >> > I have created JIRA issue https://issues.apache.org/jira > >> /browse/MINIFI-301 to > >> > track this effort. > >> > > >> > Please look for an RC2 later today. > >> > > >> > Thanks and apologies, > >> > Aldrin > >> > > >> > > >> > On May 5, 2017, at 11:40, Aldrin Piri <ald...@apache.org> wrote: > >> > > >> > Hello Apache NiFi Community, > >> > > >> > I am pleased to be calling this vote for the source release of Apache > >> NiFi > >> > MiNiFi C++, nifi-minifi-cpp-0.2.0. > >> > > >> > The source archive, signature, and digests can be located at: > >> > > >> > Source Archive: > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi- > >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz > >> > GPG armored signature: > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi- > >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.asc > >> > Source MD5: > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi- > >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.md5 > >> > Source SHA1: > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi- > >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.sha1 > >> > Source SHA256: > >> > https://dist.apache.org/repos/dist/dev/nifi/nifi- > >> > minifi-cpp/0.2.0/nifi-minifi-cpp-0.2.0-source.tar.gz.sha256 > >> > > >> > The Git tag is minifi-cpp-0.2.0-RC1 > >> > The Git commit hash is b8103f03998820449c24502fa61c224c2e39e098 > >> > * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp. > >> > git;a=commit;h=b8103f03998820449c24502fa61c224c2e39e098 > >> > * https://github.com/apache/nifi-minifi-cpp/commit/ > >> > b8103f03998820449c24502fa61c224c2e39e098 > >> > > >> > Checksums of nifi-minifi-cpp-0.2.0-source.tar.gz: > >> > MD5: 4aeb83102e95a3d9c3601d1771e67106 > >> > SHA1: f6501f87bde981e31430b13b635bee944d4b3ab3 > >> > SHA256: 8d97eb17c328637058040357523ca99984b4dcfce77d3b5f81128e1f165a > >> f081 > >> > > >> > Release artifacts are signed with the following key: > >> > https://people.apache.org/keys/committer/aldrin > >> > > >> > KEYS file available here: > >> > https://dist.apache.org/repos/dist/release/nifi/KEYS > >> > > >> > 63 issues were closed/resolved for this release: > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > >> > version=12338790&projectId=12319921 > >> > > >> > Release note highlights can be found here: > >> > https://cwiki.apache.org/confluence/display/MINIFI/ > >> > Release+Notes#ReleaseNotes-Versioncpp-0.2.0 > >> > > >> > The vote will be extended to accommodate going into the weekend and > will > >> > close 9 May at Noon EDT [1]. > >> > > >> > Please download the release candidate and evaluate the necessary items > >> > including checking hashes, signatures, build from source, and test. > Then > >> > please vote: > >> > > >> > [ ] +1 Release this package as nifi-minifi-cpp-0.2.0 > >> > [ ] +0 no opinion > >> > [ ] -1 Do not release this package because... > >> > > >> > Thanks! > >> > > >> > [1] You can determine this time for your local time zone at > >> > https://s.apache.org/minifi-cpp-0.2.0-rc1-close > >> > > >> > > >> > > >> > > > > > -- Joseph
