Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
I think I have fixed all the license problems that Robbie pointed out. The code is now checked into master I added a file, .rat-excludes, to the base folder and it includes the js files whose licenses I have explicitly copied into the main LICENSE file. - Original Message - > From: "Robbie Gemmell" <robbie.gemm...@gmail.com> > To: users@qpid.apache.org > Sent: Tuesday, April 4, 2017 6:42:44 AM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > I gave the router a try out, building against Proton 0.17.0. The build > completed fine, all tests passed, and I ran the Qpid JMS HelloWorld > against the built router. > > The signature and checksums verified fine, though the .sha512 checksum > file should be renamed with .sha extension for consistency with the > release policy and the other components that moved to SHA512 > checksums. > > Giving the release archive a look over, I noticed various license > related issues with the content: > - One file, tooltipsy.min.js, indicates it is GPLv2, which is > considered Category X > (https://www.apache.org/legal/resolved.html#category-x) meaning it > can't be included and needs removed prior to release. tooltipsy.min.js has been removed and is no longer in the source tree (thanks Ernie) > - Several other files need called out in the LICENCE file with detail > of their licence terms since they aren't ALv2. > - There are a number of files that lack a licence header that should > have one. See the RAT output summary below, though note this includes I have added license header to several files and checked them into master branch. > all the non-ALv2 files since we dont have an excludes list to reduce > the noise where actually appropriate. For the mass of JSON files, I > guess it depends how they are used given JSON doesn't strictly support > comments (though many impls do), though 'test data that would cause > failure with a header' is an allowed exception: > https://www.apache.org/legal/src-headers.html#faq-exceptions. If it The JSON files cannot have the license header and they confirm to https://www.apache.org/legal/src-headers.html#faq-exceptions I have added a file to the base folder called .rat-excludes and I have added the json files to it. The RAT tool when run in the future must use this .rat-excludes file. This file also includes several third party javascript files whose licenses I have now copied into the main LICENSE file. Robbie, please take a look at the .rat-excludes and the LICENSE file and let me know if there is something I added that should not be there. When I ran the RAT tool on the latest master using the .rat-excludes, it passed. > works, we should probably add it if only because it greatly cuts down > the noise. There is a short version of the source header for use in > very select cases where the full header might not be suited: > https://www.apache.org/legal/src-headers.html#is-a-short-form-of-the-source-header-available > > We run nightly RAT checks in CI for the java components since RAT is > available to their maven builds simply from inheriting the apache > parent pom, so all we need to do is configure an excludes list entries > as appropriate and run the goal. It would be worth setting up similar > jobs for the other components as well to help avoid getting into this > situation in future. This could either be done just using the RAT jar, > or generating a simple pom within the CI job, or various other ways (I > believe there are perhaps even tailored Buildbot jobs available for > this). I am looking into how we can add RAT to our CI jobs since we don't use Maven. Thanks. > > Robbie > > * > Summary > --- > Generated at: 2017-04-04T10:14:23+01:00 > Notes: 9 > Binaries: 37 > Archives: 0 > Standards: 682 > > Apache Licensed: 352 > Generated Documents: 0 > > JavaDocs are generated and so license header is optional > Generated files do not required license headers > > 330 Unknown Licenses > > *** > > Unapproved licenses: > > qpid-dispatch-0.8.0/.reviewboardrc > qpid-dispatch-0.8.0/.travis.yml > qpid-dispatch-0.8.0/VERSION.txt > qpid-dispatch-0.8.0/reconfigure.in > qpid-dispatch-0.8.0/bin/find_ports.sh > qpid-dispatch-0.8.0/console/dispatch-dashboard/MANIFEST.in > qpid-dispatch-0.8.0/console/dispatch-dashboard/README.rst > qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/__init__.py > qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/overv/__init__.py > > qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/overv/templates/overv/index.html > > qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/d
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
- Original Message - > From: "Ted Ross" <tr...@redhat.com> > To: users@qpid.apache.org > Sent: Tuesday, April 4, 2017 1:15:48 PM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > Just for the record... I'm waiting for the Adel/Ganesh issues to shake > out before cutting an RC2 and starting a vote. The test failure issues reported by Adel on RHEL 6.4 have been fixed on master branch. I am looking into the Solaris failures but that should not stop us from doing an RC2 after we address the licensing issues that Robbie pointed out. Thanks. > > -Ted > > On 04/04/2017 12:55 PM, Adel Boutros wrote: > > Hello Ganesh, > > > > > > I have applied your patch and it works as expected. > > > > > > Regarding Solaris, do you need extra information for analyzing? > > > > > > Regards, > > > > Adel > > > > > > From: Ganesh Murthy <gmur...@redhat.com> > > Sent: Tuesday, April 4, 2017 1:48:07 PM > > To: users@qpid.apache.org > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > Hi Adel, > > I sent out an email to you before I saw our own Travis build indicated > > that it failed the same tests that you were seeing. I apologize. This > > pull request - https://github.com/apache/qpid-dispatch/pull/158/files > > - should work for you on RHEL 6.4. This PR passes on Travis as well as > > seen here - > > > > https://travis-ci.org/apache/qpid-dispatch/builds/218223226 > > > > Thanks. > > > > - Original Message - > >> From: "Adel Boutros" <adelbout...@live.com> > >> To: users@qpid.apache.org > >> Sent: Monday, April 3, 2017 12:57:37 PM > >> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > >> > >> Hello Ganesh, > >> > >> > >> Your pull request fixed one of the 3 failing tests > >> (system_tests_protocol_family). The others still have the same errors: > >> > >> 12 - router_policy_test (Failed) > >> 18 - system_tests_policy (Failed) > >> > >> > >> Regards, > >> > >> Adel > >> > >> > >> From: Ganesh Murthy <gmur...@redhat.com> > >> Sent: Monday, April 3, 2017 6:02:31 PM > >> To: users@qpid.apache.org > >> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > >> > >> Hi Adel, > >> I believe this pull request - > >> https://github.com/apache/qpid-dispatch/pull/157 - must fix the test > >> failures you are seeing on RHEL 6.4. Can you please try applying it? > >> > >> As for the Solaris test failures, there seem to be a whole bunch of them. > >> I > >> have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738 > >> > >> I am not sure we can get to them before the 0.8.0 release. > >> > >> Thanks. > >> > >> - Original Message - > >>> From: "Adel Boutros" <adelbout...@live.com> > >>> To: users@qpid.apache.org > >>> Sent: Friday, March 31, 2017 3:55:32 AM > >>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > >>> > >>> > >>> > >>> Hello Ganesh, > >>> > >>> > >>> > >>> > >>> Please find attached the 3 build logs of the dispatch router 0.8.0 on > >>> Linux > >>> (Red Hat 6.4), Solaris x86 and Solaris Sparc. > >>> > >>> Please note we are using Proton 0.16.0 with only C++ bindings activated. > >>> > >>> > >>> > >>> > >>> PS: The good news is the code compiles on all 3 OSes but it's the tests > >>> which > >>> are failing. We consider this as a big step forward compared to the > >>> previous > >>> versions where the code didn't even compile on Solaris. > >>> > >>> > >>> > >>> > >>> Regards, > >>> > >>> Adel > >>> > >>> From: Ganesh Murthy <gmur...@redhat.com> > >>> Sent: Thursday, March 30, 2017 3:10:00 PM > >>> To: users@qpid.apache.org > >>> Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > >>> > >>> > >>> - Original Message - > >>>> From: "Adel Boutros" <adelbout...@live.com>
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
Just for the record... I'm waiting for the Adel/Ganesh issues to shake out before cutting an RC2 and starting a vote. -Ted On 04/04/2017 12:55 PM, Adel Boutros wrote: Hello Ganesh, I have applied your patch and it works as expected. Regarding Solaris, do you need extra information for analyzing? Regards, Adel From: Ganesh Murthy <gmur...@redhat.com> Sent: Tuesday, April 4, 2017 1:48:07 PM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hi Adel, I sent out an email to you before I saw our own Travis build indicated that it failed the same tests that you were seeing. I apologize. This pull request - https://github.com/apache/qpid-dispatch/pull/158/files - should work for you on RHEL 6.4. This PR passes on Travis as well as seen here - https://travis-ci.org/apache/qpid-dispatch/builds/218223226 Thanks. - Original Message - From: "Adel Boutros" <adelbout...@live.com> To: users@qpid.apache.org Sent: Monday, April 3, 2017 12:57:37 PM Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hello Ganesh, Your pull request fixed one of the 3 failing tests (system_tests_protocol_family). The others still have the same errors: 12 - router_policy_test (Failed) 18 - system_tests_policy (Failed) Regards, Adel From: Ganesh Murthy <gmur...@redhat.com> Sent: Monday, April 3, 2017 6:02:31 PM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hi Adel, I believe this pull request - https://github.com/apache/qpid-dispatch/pull/157 - must fix the test failures you are seeing on RHEL 6.4. Can you please try applying it? As for the Solaris test failures, there seem to be a whole bunch of them. I have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738 I am not sure we can get to them before the 0.8.0 release. Thanks. - Original Message - From: "Adel Boutros" <adelbout...@live.com> To: users@qpid.apache.org Sent: Friday, March 31, 2017 3:55:32 AM Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hello Ganesh, Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux (Red Hat 6.4), Solaris x86 and Solaris Sparc. Please note we are using Proton 0.16.0 with only C++ bindings activated. PS: The good news is the code compiles on all 3 OSes but it's the tests which are failing. We consider this as a big step forward compared to the previous versions where the code didn't even compile on Solaris. Regards, Adel From: Ganesh Murthy <gmur...@redhat.com> Sent: Thursday, March 30, 2017 3:10:00 PM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 - Original Message - From: "Adel Boutros" <adelbout...@live.com> To: users@qpid.apache.org Sent: Thursday, March 30, 2017 9:04:01 AM Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 I rechecked quickly and I have different behaviors on different OSes. * Linux : Can you please let us know what Linux flavor you are using so we can try locally? router_policy_test and system_tests_protocol_family failing as stated previously Please also send the complete output of the failing tests. *Solaris: Only router_policy_test is failing. For system_tests_protocol_family, I have the message "Skipping test..IPV6 not enabled" We have some other test failures on Solaris and Linux but we will need to debug them and we won't have time at the moment for them. I can send you a report with the failures if you wish. This is the commit that fixed DISPATCH-216 on master - https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036 I verified that the above commit is present in the Qpid Dispatch Router 0.8.0 Release Candidate 1 qpid-dispatch-0.8.0.tar.gz Regards, Adel From: Ted Ross <tr...@redhat.com> Sent: Thursday, March 30, 2017 2:48:10 PM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Adel, The commits associated with that Jira and PR #140 are included in this release candidate. We'll need to investigate whether it regressed again or if the commit didn't fix the problem. -Ted On 03/30/2017 11:30 AM, Adel Boutros wrote: Hello Ted, I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it doens't seem to be the case. Ganesh was working on fixing those. Do you confirm they are not included? ( http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571 ) I launched the CI on the release candidate and got the same IPv6 failures as before The following tests FAILED with ipv6 errors: 12 - router_policy_test (Failed) 19 - system_tests_protocol_family (Failed) 12: Test command: /p
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
Hello Ganesh, I have applied your patch and it works as expected. Regarding Solaris, do you need extra information for analyzing? Regards, Adel From: Ganesh Murthy <gmur...@redhat.com> Sent: Tuesday, April 4, 2017 1:48:07 PM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hi Adel, I sent out an email to you before I saw our own Travis build indicated that it failed the same tests that you were seeing. I apologize. This pull request - https://github.com/apache/qpid-dispatch/pull/158/files - should work for you on RHEL 6.4. This PR passes on Travis as well as seen here - https://travis-ci.org/apache/qpid-dispatch/builds/218223226 Thanks. - Original Message - > From: "Adel Boutros" <adelbout...@live.com> > To: users@qpid.apache.org > Sent: Monday, April 3, 2017 12:57:37 PM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > Hello Ganesh, > > > Your pull request fixed one of the 3 failing tests > (system_tests_protocol_family). The others still have the same errors: > > 12 - router_policy_test (Failed) > 18 - system_tests_policy (Failed) > > > Regards, > > Adel > > > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Monday, April 3, 2017 6:02:31 PM > To: users@qpid.apache.org > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > Hi Adel, > I believe this pull request - > https://github.com/apache/qpid-dispatch/pull/157 - must fix the test > failures you are seeing on RHEL 6.4. Can you please try applying it? > > As for the Solaris test failures, there seem to be a whole bunch of them. I > have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738 > > I am not sure we can get to them before the 0.8.0 release. > > Thanks. > > - Original Message ----- > > From: "Adel Boutros" <adelbout...@live.com> > > To: users@qpid.apache.org > > Sent: Friday, March 31, 2017 3:55:32 AM > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > > > > > Hello Ganesh, > > > > > > > > > > Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux > > (Red Hat 6.4), Solaris x86 and Solaris Sparc. > > > > Please note we are using Proton 0.16.0 with only C++ bindings activated. > > > > > > > > > > PS: The good news is the code compiles on all 3 OSes but it's the tests > > which > > are failing. We consider this as a big step forward compared to the > > previous > > versions where the code didn't even compile on Solaris. > > > > > > > > > > Regards, > > > > Adel > > > > From: Ganesh Murthy <gmur...@redhat.com> > > Sent: Thursday, March 30, 2017 3:10:00 PM > > To: users@qpid.apache.org > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > > > - Original Message - > > > From: "Adel Boutros" <adelbout...@live.com> > > > To: users@qpid.apache.org > > > Sent: Thursday, March 30, 2017 9:04:01 AM > > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > > > I rechecked quickly and I have different behaviors on different OSes. > > > > > > > > > * Linux : > > > > > Can you please let us know what Linux flavor you are using so we can try > > locally? > > > router_policy_test and system_tests_protocol_family failing as stated > > > previously > > > > > Please also send the complete output of the failing tests. > > > > > > *Solaris: > > > > > > Only router_policy_test is failing. > > > > > > For system_tests_protocol_family, I have the message "Skipping test..IPV6 > > > not > > > enabled" > > > > > > > > > We have some other test failures on Solaris and Linux but we will need to > > > debug them and we won't have time at the moment for them. I can send you > > > a > > > report with the failures if you wish. > > > > > This is the commit that fixed DISPATCH-216 on master - > > https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036 > > I verified that the above commit is present in the Qpid Dispatch Router > > 0.8.0 > > Release Candidate 1 qpid-dispatch-0.8.0.tar.gz > > > > > > Regards, > > > > > > Adel > > > > > > > > > From: Ted Ross <t
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
Hi Adel, I sent out an email to you before I saw our own Travis build indicated that it failed the same tests that you were seeing. I apologize. This pull request - https://github.com/apache/qpid-dispatch/pull/158/files - should work for you on RHEL 6.4. This PR passes on Travis as well as seen here - https://travis-ci.org/apache/qpid-dispatch/builds/218223226 Thanks. - Original Message - > From: "Adel Boutros" <adelbout...@live.com> > To: users@qpid.apache.org > Sent: Monday, April 3, 2017 12:57:37 PM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > Hello Ganesh, > > > Your pull request fixed one of the 3 failing tests > (system_tests_protocol_family). The others still have the same errors: > > 12 - router_policy_test (Failed) > 18 - system_tests_policy (Failed) > > > Regards, > > Adel > > > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Monday, April 3, 2017 6:02:31 PM > To: users@qpid.apache.org > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > Hi Adel, > I believe this pull request - > https://github.com/apache/qpid-dispatch/pull/157 - must fix the test > failures you are seeing on RHEL 6.4. Can you please try applying it? > > As for the Solaris test failures, there seem to be a whole bunch of them. I > have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738 > > I am not sure we can get to them before the 0.8.0 release. > > Thanks. > > - Original Message - > > From: "Adel Boutros" <adelbout...@live.com> > > To: users@qpid.apache.org > > Sent: Friday, March 31, 2017 3:55:32 AM > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > > > > > Hello Ganesh, > > > > > > > > > > Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux > > (Red Hat 6.4), Solaris x86 and Solaris Sparc. > > > > Please note we are using Proton 0.16.0 with only C++ bindings activated. > > > > > > > > > > PS: The good news is the code compiles on all 3 OSes but it's the tests > > which > > are failing. We consider this as a big step forward compared to the > > previous > > versions where the code didn't even compile on Solaris. > > > > > > > > > > Regards, > > > > Adel > > > > From: Ganesh Murthy <gmur...@redhat.com> > > Sent: Thursday, March 30, 2017 3:10:00 PM > > To: users@qpid.apache.org > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > > > - Original Message - > > > From: "Adel Boutros" <adelbout...@live.com> > > > To: users@qpid.apache.org > > > Sent: Thursday, March 30, 2017 9:04:01 AM > > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > > > I rechecked quickly and I have different behaviors on different OSes. > > > > > > > > > * Linux : > > > > > Can you please let us know what Linux flavor you are using so we can try > > locally? > > > router_policy_test and system_tests_protocol_family failing as stated > > > previously > > > > > Please also send the complete output of the failing tests. > > > > > > *Solaris: > > > > > > Only router_policy_test is failing. > > > > > > For system_tests_protocol_family, I have the message "Skipping test..IPV6 > > > not > > > enabled" > > > > > > > > > We have some other test failures on Solaris and Linux but we will need to > > > debug them and we won't have time at the moment for them. I can send you > > > a > > > report with the failures if you wish. > > > > > This is the commit that fixed DISPATCH-216 on master - > > https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036 > > I verified that the above commit is present in the Qpid Dispatch Router > > 0.8.0 > > Release Candidate 1 qpid-dispatch-0.8.0.tar.gz > > > > > > Regards, > > > > > > Adel > > > > > > > > > From: Ted Ross <tr...@redhat.com> > > > Sent: Thursday, March 30, 2017 2:48:10 PM > > > To: users@qpid.apache.org > > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > > > Adel, > > > > > > The commits associated with that Jira and PR #140 are included in this > >
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
I gave the router a try out, building against Proton 0.17.0. The build completed fine, all tests passed, and I ran the Qpid JMS HelloWorld against the built router. The signature and checksums verified fine, though the .sha512 checksum file should be renamed with .sha extension for consistency with the release policy and the other components that moved to SHA512 checksums. Giving the release archive a look over, I noticed various license related issues with the content: - One file, tooltipsy.min.js, indicates it is GPLv2, which is considered Category X (https://www.apache.org/legal/resolved.html#category-x) meaning it can't be included and needs removed prior to release. - Several other files need called out in the LICENCE file with detail of their licence terms since they aren't ALv2. - There are a number of files that lack a licence header that should have one. See the RAT output summary below, though note this includes all the non-ALv2 files since we dont have an excludes list to reduce the noise where actually appropriate. For the mass of JSON files, I guess it depends how they are used given JSON doesn't strictly support comments (though many impls do), though 'test data that would cause failure with a header' is an allowed exception: https://www.apache.org/legal/src-headers.html#faq-exceptions. If it works, we should probably add it if only because it greatly cuts down the noise. There is a short version of the source header for use in very select cases where the full header might not be suited: https://www.apache.org/legal/src-headers.html#is-a-short-form-of-the-source-header-available We run nightly RAT checks in CI for the java components since RAT is available to their maven builds simply from inheriting the apache parent pom, so all we need to do is configure an excludes list entries as appropriate and run the goal. It would be worth setting up similar jobs for the other components as well to help avoid getting into this situation in future. This could either be done just using the RAT jar, or generating a simple pom within the CI job, or various other ways (I believe there are perhaps even tailored Buildbot jobs available for this). Robbie * Summary --- Generated at: 2017-04-04T10:14:23+01:00 Notes: 9 Binaries: 37 Archives: 0 Standards: 682 Apache Licensed: 352 Generated Documents: 0 JavaDocs are generated and so license header is optional Generated files do not required license headers 330 Unknown Licenses *** Unapproved licenses: qpid-dispatch-0.8.0/.reviewboardrc qpid-dispatch-0.8.0/.travis.yml qpid-dispatch-0.8.0/VERSION.txt qpid-dispatch-0.8.0/reconfigure.in qpid-dispatch-0.8.0/bin/find_ports.sh qpid-dispatch-0.8.0/console/dispatch-dashboard/MANIFEST.in qpid-dispatch-0.8.0/console/dispatch-dashboard/README.rst qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/__init__.py qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/overv/__init__.py qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/overv/templates/overv/index.html qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/connect.json qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/jquery.dynatree.min.js qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/d3.v3.min.js qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/rhea-min.js qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/slider.js qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/tooltipsy.min.js qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/lib/ui-grid.js qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/topology/download-dialog-template.html qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/static/dashboard/dispatch/topology/node-config-template.html qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/templates/dispatch/base.html qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/topology/__init__.py qpid-dispatch-0.8.0/console/dispatch-dashboard/dispatch/topology/templates/topology/index.html qpid-dispatch-0.8.0/console/dispatch-dashboard/enabled/_4030_dispatch_overv_panel.py qpid-dispatch-0.8.0/console/dispatch-dashboard/enabled/_4050_dispatch_topology_panel.py qpid-dispatch-0.8.0/console/hawtio/README.md qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/index.html qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplListChart.html qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplListTree.html qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/html/tmplOverviewTree.html qpid-dispatch-0.8.0/console/hawtio/src/main/webapp/plugin/lib/rhea-min.js
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
Hello Ganesh, Your pull request fixed one of the 3 failing tests (system_tests_protocol_family). The others still have the same errors: 12 - router_policy_test (Failed) 18 - system_tests_policy (Failed) Regards, Adel From: Ganesh Murthy <gmur...@redhat.com> Sent: Monday, April 3, 2017 6:02:31 PM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hi Adel, I believe this pull request - https://github.com/apache/qpid-dispatch/pull/157 - must fix the test failures you are seeing on RHEL 6.4. Can you please try applying it? As for the Solaris test failures, there seem to be a whole bunch of them. I have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738 I am not sure we can get to them before the 0.8.0 release. Thanks. - Original Message - > From: "Adel Boutros" <adelbout...@live.com> > To: users@qpid.apache.org > Sent: Friday, March 31, 2017 3:55:32 AM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > Hello Ganesh, > > > > > Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux > (Red Hat 6.4), Solaris x86 and Solaris Sparc. > > Please note we are using Proton 0.16.0 with only C++ bindings activated. > > > > > PS: The good news is the code compiles on all 3 OSes but it's the tests which > are failing. We consider this as a big step forward compared to the previous > versions where the code didn't even compile on Solaris. > > > > > Regards, > > Adel > > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Thursday, March 30, 2017 3:10:00 PM > To: users@qpid.apache.org > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > - Original Message - > > From: "Adel Boutros" <adelbout...@live.com> > > To: users@qpid.apache.org > > Sent: Thursday, March 30, 2017 9:04:01 AM > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > I rechecked quickly and I have different behaviors on different OSes. > > > > > > * Linux : > > > Can you please let us know what Linux flavor you are using so we can try > locally? > > router_policy_test and system_tests_protocol_family failing as stated > > previously > > > Please also send the complete output of the failing tests. > > > > *Solaris: > > > > Only router_policy_test is failing. > > > > For system_tests_protocol_family, I have the message "Skipping test..IPV6 > > not > > enabled" > > > > > > We have some other test failures on Solaris and Linux but we will need to > > debug them and we won't have time at the moment for them. I can send you a > > report with the failures if you wish. > > > This is the commit that fixed DISPATCH-216 on master - > https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036 > I verified that the above commit is present in the Qpid Dispatch Router 0.8.0 > Release Candidate 1 qpid-dispatch-0.8.0.tar.gz > > > > Regards, > > > > Adel > > > > > > From: Ted Ross <tr...@redhat.com> > > Sent: Thursday, March 30, 2017 2:48:10 PM > > To: users@qpid.apache.org > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > Adel, > > > > The commits associated with that Jira and PR #140 are included in this > > release candidate. We'll need to investigate whether it regressed again > > or if the commit didn't fix the problem. > > > > -Ted > > > > On 03/30/2017 11:30 AM, Adel Boutros wrote: > > > Hello Ted, > > > > > > > > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but > > > it > > > doens't seem to be the case. Ganesh was working on fixing those. > > > > > > Do you confirm they are not included? > > > ( > > > http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571 > > > ) > > > > > > > > > I launched the CI on the release candidate and got the same IPv6 failures > > > as before > > > > > > > > > The following tests FAILED with ipv6 errors: > > > 12 - router_policy_test (Failed) > > > 19 - system_tests_protocol_family (Failed) > > > > > > > > > > > > 12: Test command: /python278/bin/python > > > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" > > > "
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
Hi Adel, I believe this pull request - https://github.com/apache/qpid-dispatch/pull/157 - must fix the test failures you are seeing on RHEL 6.4. Can you please try applying it? As for the Solaris test failures, there seem to be a whole bunch of them. I have created a JIRA - https://issues.apache.org/jira/browse/DISPATCH-738 I am not sure we can get to them before the 0.8.0 release. Thanks. - Original Message - > From: "Adel Boutros" <adelbout...@live.com> > To: users@qpid.apache.org > Sent: Friday, March 31, 2017 3:55:32 AM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > Hello Ganesh, > > > > > Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux > (Red Hat 6.4), Solaris x86 and Solaris Sparc. > > Please note we are using Proton 0.16.0 with only C++ bindings activated. > > > > > PS: The good news is the code compiles on all 3 OSes but it's the tests which > are failing. We consider this as a big step forward compared to the previous > versions where the code didn't even compile on Solaris. > > > > > Regards, > > Adel > > From: Ganesh Murthy <gmur...@redhat.com> > Sent: Thursday, March 30, 2017 3:10:00 PM > To: users@qpid.apache.org > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > - Original Message - > > From: "Adel Boutros" <adelbout...@live.com> > > To: users@qpid.apache.org > > Sent: Thursday, March 30, 2017 9:04:01 AM > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > I rechecked quickly and I have different behaviors on different OSes. > > > > > > * Linux : > > > Can you please let us know what Linux flavor you are using so we can try > locally? > > router_policy_test and system_tests_protocol_family failing as stated > > previously > > > Please also send the complete output of the failing tests. > > > > *Solaris: > > > > Only router_policy_test is failing. > > > > For system_tests_protocol_family, I have the message "Skipping test..IPV6 > > not > > enabled" > > > > > > We have some other test failures on Solaris and Linux but we will need to > > debug them and we won't have time at the moment for them. I can send you a > > report with the failures if you wish. > > > This is the commit that fixed DISPATCH-216 on master - > https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036 > I verified that the above commit is present in the Qpid Dispatch Router 0.8.0 > Release Candidate 1 qpid-dispatch-0.8.0.tar.gz > > > > Regards, > > > > Adel > > > > > > From: Ted Ross <tr...@redhat.com> > > Sent: Thursday, March 30, 2017 2:48:10 PM > > To: users@qpid.apache.org > > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > Adel, > > > > The commits associated with that Jira and PR #140 are included in this > > release candidate. We'll need to investigate whether it regressed again > > or if the commit didn't fix the problem. > > > > -Ted > > > > On 03/30/2017 11:30 AM, Adel Boutros wrote: > > > Hello Ted, > > > > > > > > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but > > > it > > > doens't seem to be the case. Ganesh was working on fixing those. > > > > > > Do you confirm they are not included? > > > ( > > > http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571 > > > ) > > > > > > > > > I launched the CI on the release candidate and got the same IPv6 failures > > > as before > > > > > > > > > The following tests FAILED with ipv6 errors: > > > 12 - router_policy_test (Failed) > > > 19 - system_tests_protocol_family (Failed) > > > > > > > > > > > > 12: Test command: /python278/bin/python > > > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" > > > "unittest" > > > "-v" "router_policy_test" > > > 12: Test timeout computed to be: 1500 > > > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' > > > is > > > invalid: Policy vhost \'photoserver\' user group \'superuser\' option > > > \'remoteHosts\' connectionOption \'::1\' failed to trans
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
Small correction: We are using Proton 0.16.0 with only C++ and Python bindings activated. From: Adel Boutros Sent: Friday, March 31, 2017 9:55:32 AM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Hello Ganesh, Please find attached the 3 build logs of the dispatch router 0.8.0 on Linux (Red Hat 6.4), Solaris x86 and Solaris Sparc. Please note we are using Proton 0.16.0 with only C++ bindings activated. PS: The good news is the code compiles on all 3 OSes but it's the tests which are failing. We consider this as a big step forward compared to the previous versions where the code didn't even compile on Solaris. Regards, Adel From: Ganesh Murthy <gmur...@redhat.com> Sent: Thursday, March 30, 2017 3:10:00 PM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 - Original Message - > From: "Adel Boutros" <adelbout...@live.com> > To: users@qpid.apache.org > Sent: Thursday, March 30, 2017 9:04:01 AM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > I rechecked quickly and I have different behaviors on different OSes. > > > * Linux : > Can you please let us know what Linux flavor you are using so we can try locally? > router_policy_test and system_tests_protocol_family failing as stated > previously > Please also send the complete output of the failing tests. > > *Solaris: > > Only router_policy_test is failing. > > For system_tests_protocol_family, I have the message "Skipping test..IPV6 not > enabled" > > > We have some other test failures on Solaris and Linux but we will need to > debug them and we won't have time at the moment for them. I can send you a > report with the failures if you wish. > This is the commit that fixed DISPATCH-216 on master - https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036 I verified that the above commit is present in the Qpid Dispatch Router 0.8.0 Release Candidate 1 qpid-dispatch-0.8.0.tar.gz > > Regards, > > Adel > > > From: Ted Ross <tr...@redhat.com> > Sent: Thursday, March 30, 2017 2:48:10 PM > To: users@qpid.apache.org > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > Adel, > > The commits associated with that Jira and PR #140 are included in this > release candidate. We'll need to investigate whether it regressed again > or if the commit didn't fix the problem. > > -Ted > > On 03/30/2017 11:30 AM, Adel Boutros wrote: > > Hello Ted, > > > > > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it > > doens't seem to be the case. Ganesh was working on fixing those. > > > > Do you confirm they are not included? > > (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571) > > > > > > I launched the CI on the release candidate and got the same IPv6 failures > > as before > > > > > > The following tests FAILED with ipv6 errors: > > 12 - router_policy_test (Failed) > > 19 - system_tests_protocol_family (Failed) > > > > > > > > 12: Test command: /python278/bin/python > > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest" > > "-v" "router_policy_test" > > 12: Test timeout computed to be: 1500 > > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is > > invalid: Policy vhost \'photoserver\' user group \'superuser\' option > > \'remoteHosts\' connectionOption \'::1\' failed to translate: > > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct: > > \\\'::1\\\' did not resolve to one of the supported address > > family"\\\'\'\'.' > > > > > > 19: error: [Errno 97] Address family not supported by protocol > > > > > > Regards, > > > > Adel > > > > > > From: Ted Ross <tr...@redhat.com> > > Sent: Wednesday, March 29, 2017 1:32:42 PM > > To: users@qpid.apache.org > > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for > > evaluation. > > > > Build Artifacts: > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/ > > > > New Features: > > > > DISPATCH-103 - Websocket Listeners > > DISPATCH-195 - Add support for transactional messages in t
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
- Original Message - > From: "Adel Boutros" <adelbout...@live.com> > To: users@qpid.apache.org > Sent: Thursday, March 30, 2017 9:04:01 AM > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > I rechecked quickly and I have different behaviors on different OSes. > > > * Linux : > Can you please let us know what Linux flavor you are using so we can try locally? > router_policy_test and system_tests_protocol_family failing as stated > previously > Please also send the complete output of the failing tests. > > *Solaris: > > Only router_policy_test is failing. > > For system_tests_protocol_family, I have the message "Skipping test..IPV6 not > enabled" > > > We have some other test failures on Solaris and Linux but we will need to > debug them and we won't have time at the moment for them. I can send you a > report with the failures if you wish. > This is the commit that fixed DISPATCH-216 on master - https://github.com/apache/qpid-dispatch/commit/0a60abbf6b06048e1ac7a71a48da82145fa77036 I verified that the above commit is present in the Qpid Dispatch Router 0.8.0 Release Candidate 1 qpid-dispatch-0.8.0.tar.gz > > Regards, > > Adel > > > From: Ted Ross <tr...@redhat.com> > Sent: Thursday, March 30, 2017 2:48:10 PM > To: users@qpid.apache.org > Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > Adel, > > The commits associated with that Jira and PR #140 are included in this > release candidate. We'll need to investigate whether it regressed again > or if the commit didn't fix the problem. > > -Ted > > On 03/30/2017 11:30 AM, Adel Boutros wrote: > > Hello Ted, > > > > > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it > > doens't seem to be the case. Ganesh was working on fixing those. > > > > Do you confirm they are not included? > > (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571) > > > > > > I launched the CI on the release candidate and got the same IPv6 failures > > as before > > > > > > The following tests FAILED with ipv6 errors: > > 12 - router_policy_test (Failed) > > 19 - system_tests_protocol_family (Failed) > > > > > > > > 12: Test command: /python278/bin/python > > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest" > > "-v" "router_policy_test" > > 12: Test timeout computed to be: 1500 > > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is > > invalid: Policy vhost \'photoserver\' user group \'superuser\' option > > \'remoteHosts\' connectionOption \'::1\' failed to translate: > > \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct: > > \\\'::1\\\' did not resolve to one of the supported address > > family"\\\'\'\'.' > > > > > > 19: error: [Errno 97] Address family not supported by protocol > > > > > > Regards, > > > > Adel > > > > > > From: Ted Ross <tr...@redhat.com> > > Sent: Wednesday, March 29, 2017 1:32:42 PM > > To: users@qpid.apache.org > > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > > > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for > > evaluation. > > > > Build Artifacts: > > > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/ > > > > New Features: > > > > DISPATCH-103 - Websocket Listeners > > DISPATCH-195 - Add support for transactional messages in the Router > > DISPATCH-441 - Support password environment variable in qdrouter > > config > > DISPATCH-467 - Terminus renaming for autoLinks > > DISPATCH-529 - Address annotation for Multi-Tenancy > > DISPATCH-726 - Connection Property for Failover Servers > > > > Improvements: > > > > DISPATCH-113 - expose NodeTracker::last_topology_change in management > > DISPATCH-542 - Popup text for clients should indicate if the client > > is a sender or receiver > > DISPATCH-543 - Initial load of topology page fetches too much > > information > > DISPATCH-544 - Add ability to hide the info panel on the left of > > the topology page > > DISPATCH-552 - Allow only one tree node to be expanded if there is > > a large number of routers > > DISPATCH-553 - Add
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
I rechecked quickly and I have different behaviors on different OSes. * Linux : router_policy_test and system_tests_protocol_family failing as stated previously *Solaris: Only router_policy_test is failing. For system_tests_protocol_family, I have the message "Skipping test..IPV6 not enabled" We have some other test failures on Solaris and Linux but we will need to debug them and we won't have time at the moment for them. I can send you a report with the failures if you wish. Regards, Adel From: Ted Ross <tr...@redhat.com> Sent: Thursday, March 30, 2017 2:48:10 PM To: users@qpid.apache.org Subject: Re: Qpid Dispatch Router 0.8.0 Release Candidate 1 Adel, The commits associated with that Jira and PR #140 are included in this release candidate. We'll need to investigate whether it regressed again or if the commit didn't fix the problem. -Ted On 03/30/2017 11:30 AM, Adel Boutros wrote: > Hello Ted, > > > I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it > doens't seem to be the case. Ganesh was working on fixing those. > > Do you confirm they are not included? > (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571) > > > I launched the CI on the release candidate and got the same IPv6 failures as > before > > > The following tests FAILED with ipv6 errors: > 12 - router_policy_test (Failed) > 19 - system_tests_protocol_family (Failed) > > > > 12: Test command: /python278/bin/python > "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest" > "-v" "router_policy_test" > 12: Test timeout computed to be: 1500 > 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is > invalid: Policy vhost \'photoserver\' user group \'superuser\' option > \'remoteHosts\' connectionOption \'::1\' failed to translate: \'\'HostStruct: > \\\'::1\\\' failed to resolve: \\\'"HostStruct: \\\'::1\\\' did not resolve > to one of the supported address family"\\\'\'\'.' > > > 19: error: [Errno 97] Address family not supported by protocol > > > Regards, > > Adel > > ____ > From: Ted Ross <tr...@redhat.com> > Sent: Wednesday, March 29, 2017 1:32:42 PM > To: users@qpid.apache.org > Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1 > > The first release candidate for Qpid Dispatch Router 0.8.0 is ready for > evaluation. > > Build Artifacts: > > https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/ > > New Features: > > DISPATCH-103 - Websocket Listeners > DISPATCH-195 - Add support for transactional messages in the Router > DISPATCH-441 - Support password environment variable in qdrouter config > DISPATCH-467 - Terminus renaming for autoLinks > DISPATCH-529 - Address annotation for Multi-Tenancy > DISPATCH-726 - Connection Property for Failover Servers > > Improvements: > > DISPATCH-113 - expose NodeTracker::last_topology_change in management > DISPATCH-542 - Popup text for clients should indicate if the client > is a sender or receiver > DISPATCH-543 - Initial load of topology page fetches too much > information > DISPATCH-544 - Add ability to hide the info panel on the left of > the topology page > DISPATCH-552 - Allow only one tree node to be expanded if there is > a large number of routers > DISPATCH-553 - Add statistic counter to the "log" entity to count > log events per severity > DISPATCH-559 - qdstat - Request only the columns that will be used > in the display > DISPATCH-561 - Create python program that returns fake management data > DISPATCH-568 - Iterator module cleanup > DISPATCH-570 - Add some counts to qdstat -g > DISPATCH-572 - Adding log info with proton transport id and related > remote IP/port > DISPATCH-576 - Use new log entity statistic counter in console > DISPATCH-578 - Dispatch trace logging forces all proton tracing on > DISPATCH-579 - Expose software version via management > DISPATCH-592 - Attempt to auto-login to the host:port that served > the web page > DISPATCH-597 - Log enhancements > DISPATCH-600 - Support secure websockets > DISPATCH-602 - Add a favicon to the stand-alone router site > DISPATCH-606 - Default session window is too small, causing > performance bottlenecks > DISPATCH-627 - BatchedSettlement test fails with timeout on slower > systems > DISPATCH-629 - Add a protocol-version to the inter-router protocol > to enable backward compatibi
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
Adel, The commits associated with that Jira and PR #140 are included in this release candidate. We'll need to investigate whether it regressed again or if the commit didn't fix the problem. -Ted On 03/30/2017 11:30 AM, Adel Boutros wrote: Hello Ted, I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it doens't seem to be the case. Ganesh was working on fixing those. Do you confirm they are not included? (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571) I launched the CI on the release candidate and got the same IPv6 failures as before The following tests FAILED with ipv6 errors: 12 - router_policy_test (Failed) 19 - system_tests_protocol_family (Failed) 12: Test command: /python278/bin/python "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest" "-v" "router_policy_test" 12: Test timeout computed to be: 1500 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is invalid: Policy vhost \'photoserver\' user group \'superuser\' option \'remoteHosts\' connectionOption \'::1\' failed to translate: \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct: \\\'::1\\\' did not resolve to one of the supported address family"\\\'\'\'.' 19: error: [Errno 97] Address family not supported by protocol Regards, Adel From: Ted Ross <tr...@redhat.com> Sent: Wednesday, March 29, 2017 1:32:42 PM To: users@qpid.apache.org Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1 The first release candidate for Qpid Dispatch Router 0.8.0 is ready for evaluation. Build Artifacts: https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/ New Features: DISPATCH-103 - Websocket Listeners DISPATCH-195 - Add support for transactional messages in the Router DISPATCH-441 - Support password environment variable in qdrouter config DISPATCH-467 - Terminus renaming for autoLinks DISPATCH-529 - Address annotation for Multi-Tenancy DISPATCH-726 - Connection Property for Failover Servers Improvements: DISPATCH-113 - expose NodeTracker::last_topology_change in management DISPATCH-542 - Popup text for clients should indicate if the client is a sender or receiver DISPATCH-543 - Initial load of topology page fetches too much information DISPATCH-544 - Add ability to hide the info panel on the left of the topology page DISPATCH-552 - Allow only one tree node to be expanded if there is a large number of routers DISPATCH-553 - Add statistic counter to the "log" entity to count log events per severity DISPATCH-559 - qdstat - Request only the columns that will be used in the display DISPATCH-561 - Create python program that returns fake management data DISPATCH-568 - Iterator module cleanup DISPATCH-570 - Add some counts to qdstat -g DISPATCH-572 - Adding log info with proton transport id and related remote IP/port DISPATCH-576 - Use new log entity statistic counter in console DISPATCH-578 - Dispatch trace logging forces all proton tracing on DISPATCH-579 - Expose software version via management DISPATCH-592 - Attempt to auto-login to the host:port that served the web page DISPATCH-597 - Log enhancements DISPATCH-600 - Support secure websockets DISPATCH-602 - Add a favicon to the stand-alone router site DISPATCH-606 - Default session window is too small, causing performance bottlenecks DISPATCH-627 - BatchedSettlement test fails with timeout on slower systems DISPATCH-629 - Add a protocol-version to the inter-router protocol to enable backward compatibility DISPATCH-641 - Make containerId attribute work with clients Bugs Fixed: DISPATCH-55 - Qdrouterd does not exit when service port is unavailable DISPATCH-216 - system_tests_protocol_family fails on systems with no IPv6 DISPATCH-296 - segfault on router startup DISPATCH-301 - Some unit tests fail with workerThreads are set to 4 DISPATCH-314 - If a router has a normal listener, show it in a different color on the topology page DISPATCH-324 - Improve initial layout of topology node DISPATCH-344 - memory growth after repeated calls from qdstat -m DISPATCH-352 - Crash with empty configuration file DISPATCH-355 - query fails with what seems to be the error of a previous command DISPATCH-357 - Address field is empty for link routed links in the qdstat "links" output DISPATCH-433 - Navigating to console from bookmark displays empty page with just toolbars DISPATCH-451 - [AMQP] Hard coded session capacity should be configurable DISPATCH-503 - [display_name] successful test runs have non-ascii characters in router log DISPATCH-504 - [display_name] successful test runs have
Re: Qpid Dispatch Router 0.8.0 Release Candidate 1
Hello Ted, I thought the 0.8.0 release included the fixes to ignore IPv6 tests but it doens't seem to be the case. Ganesh was working on fixing those. Do you confirm they are not included? (http://qpid.2158936.n2.nabble.com/Fwd-GitHub-qpid-dispatch-pull-request-140-DISPATCH-216-Added-code-to-skip-system-te-td7658538.html#a7658571) I launched the CI on the release candidate and got the same IPv6 failures as before The following tests FAILED with ipv6 errors: 12 - router_policy_test (Failed) 19 - system_tests_protocol_family (Failed) 12: Test command: /python278/bin/python "/dispatch-workspace/build-dir/qpid-dispatch/tests/run.py" "-m" "unittest" "-v" "router_policy_test" 12: Test timeout computed to be: 1500 12: Run python module 'unittest': PolicyError: u'Policy \'photoserver\' is invalid: Policy vhost \'photoserver\' user group \'superuser\' option \'remoteHosts\' connectionOption \'::1\' failed to translate: \'\'HostStruct: \\\'::1\\\' failed to resolve: \\\'"HostStruct: \\\'::1\\\' did not resolve to one of the supported address family"\\\'\'\'.' 19: error: [Errno 97] Address family not supported by protocol Regards, Adel From: Ted Ross <tr...@redhat.com> Sent: Wednesday, March 29, 2017 1:32:42 PM To: users@qpid.apache.org Subject: Qpid Dispatch Router 0.8.0 Release Candidate 1 The first release candidate for Qpid Dispatch Router 0.8.0 is ready for evaluation. Build Artifacts: https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/ New Features: DISPATCH-103 - Websocket Listeners DISPATCH-195 - Add support for transactional messages in the Router DISPATCH-441 - Support password environment variable in qdrouter config DISPATCH-467 - Terminus renaming for autoLinks DISPATCH-529 - Address annotation for Multi-Tenancy DISPATCH-726 - Connection Property for Failover Servers Improvements: DISPATCH-113 - expose NodeTracker::last_topology_change in management DISPATCH-542 - Popup text for clients should indicate if the client is a sender or receiver DISPATCH-543 - Initial load of topology page fetches too much information DISPATCH-544 - Add ability to hide the info panel on the left of the topology page DISPATCH-552 - Allow only one tree node to be expanded if there is a large number of routers DISPATCH-553 - Add statistic counter to the "log" entity to count log events per severity DISPATCH-559 - qdstat - Request only the columns that will be used in the display DISPATCH-561 - Create python program that returns fake management data DISPATCH-568 - Iterator module cleanup DISPATCH-570 - Add some counts to qdstat -g DISPATCH-572 - Adding log info with proton transport id and related remote IP/port DISPATCH-576 - Use new log entity statistic counter in console DISPATCH-578 - Dispatch trace logging forces all proton tracing on DISPATCH-579 - Expose software version via management DISPATCH-592 - Attempt to auto-login to the host:port that served the web page DISPATCH-597 - Log enhancements DISPATCH-600 - Support secure websockets DISPATCH-602 - Add a favicon to the stand-alone router site DISPATCH-606 - Default session window is too small, causing performance bottlenecks DISPATCH-627 - BatchedSettlement test fails with timeout on slower systems DISPATCH-629 - Add a protocol-version to the inter-router protocol to enable backward compatibility DISPATCH-641 - Make containerId attribute work with clients Bugs Fixed: DISPATCH-55 - Qdrouterd does not exit when service port is unavailable DISPATCH-216 - system_tests_protocol_family fails on systems with no IPv6 DISPATCH-296 - segfault on router startup DISPATCH-301 - Some unit tests fail with workerThreads are set to 4 DISPATCH-314 - If a router has a normal listener, show it in a different color on the topology page DISPATCH-324 - Improve initial layout of topology node DISPATCH-344 - memory growth after repeated calls from qdstat -m DISPATCH-352 - Crash with empty configuration file DISPATCH-355 - query fails with what seems to be the error of a previous command DISPATCH-357 - Address field is empty for link routed links in the qdstat "links" output DISPATCH-433 - Navigating to console from bookmark displays empty page with just toolbars DISPATCH-451 - [AMQP] Hard coded session capacity should be configurable DISPATCH-503 - [display_name] successful test runs have non-ascii characters in router log DISPATCH-504 - [display_name] successful test runs have invalid message errors in router log DISPATCH-506 - Detach with no "error" sent by router on client TCP connection dropped DISPATCH-516 - Core dump when displayname IO adapter receives message with no reply-to DISPATCH-526 -
Qpid Dispatch Router 0.8.0 Release Candidate 1
The first release candidate for Qpid Dispatch Router 0.8.0 is ready for evaluation. Build Artifacts: https://dist.apache.org/repos/dist/dev/qpid/dispatch/0.8.0-rc1/ New Features: DISPATCH-103 - Websocket Listeners DISPATCH-195 - Add support for transactional messages in the Router DISPATCH-441 - Support password environment variable in qdrouter config DISPATCH-467 - Terminus renaming for autoLinks DISPATCH-529 - Address annotation for Multi-Tenancy DISPATCH-726 - Connection Property for Failover Servers Improvements: DISPATCH-113 - expose NodeTracker::last_topology_change in management DISPATCH-542 - Popup text for clients should indicate if the client is a sender or receiver DISPATCH-543 - Initial load of topology page fetches too much information DISPATCH-544 - Add ability to hide the info panel on the left of the topology page DISPATCH-552 - Allow only one tree node to be expanded if there is a large number of routers DISPATCH-553 - Add statistic counter to the "log" entity to count log events per severity DISPATCH-559 - qdstat - Request only the columns that will be used in the display DISPATCH-561 - Create python program that returns fake management data DISPATCH-568 - Iterator module cleanup DISPATCH-570 - Add some counts to qdstat -g DISPATCH-572 - Adding log info with proton transport id and related remote IP/port DISPATCH-576 - Use new log entity statistic counter in console DISPATCH-578 - Dispatch trace logging forces all proton tracing on DISPATCH-579 - Expose software version via management DISPATCH-592 - Attempt to auto-login to the host:port that served the web page DISPATCH-597 - Log enhancements DISPATCH-600 - Support secure websockets DISPATCH-602 - Add a favicon to the stand-alone router site DISPATCH-606 - Default session window is too small, causing performance bottlenecks DISPATCH-627 - BatchedSettlement test fails with timeout on slower systems DISPATCH-629 - Add a protocol-version to the inter-router protocol to enable backward compatibility DISPATCH-641 - Make containerId attribute work with clients Bugs Fixed: DISPATCH-55 - Qdrouterd does not exit when service port is unavailable DISPATCH-216 - system_tests_protocol_family fails on systems with no IPv6 DISPATCH-296 - segfault on router startup DISPATCH-301 - Some unit tests fail with workerThreads are set to 4 DISPATCH-314 - If a router has a normal listener, show it in a different color on the topology page DISPATCH-324 - Improve initial layout of topology node DISPATCH-344 - memory growth after repeated calls from qdstat -m DISPATCH-352 - Crash with empty configuration file DISPATCH-355 - query fails with what seems to be the error of a previous command DISPATCH-357 - Address field is empty for link routed links in the qdstat "links" output DISPATCH-433 - Navigating to console from bookmark displays empty page with just toolbars DISPATCH-451 - [AMQP] Hard coded session capacity should be configurable DISPATCH-503 - [display_name] successful test runs have non-ascii characters in router log DISPATCH-504 - [display_name] successful test runs have invalid message errors in router log DISPATCH-506 - Detach with no "error" sent by router on client TCP connection dropped DISPATCH-516 - Core dump when displayname IO adapter receives message with no reply-to DISPATCH-526 - Coverity scan reported memory leaks in Qpid Dispatch 0.7.0 DISPATCH-527 - The $displayname address is currently available. It should not be available to external users DISPATCH-530 - Cannot connect using Firefox 48+ DISPATCH-534 - Node selection and location is lost when the topology changes DISPATCH-536 - Circular buffer overflow errors occur when there are a large number of routers DISPATCH-538 - Highlighted path between routers sometimes doesn't unhighlight DISPATCH-540 - Clients with both in and out links are rendered in yellow DISPATCH-541 - Highlighted path between routers contains black arrows DISPATCH-546 - Crosssection popup position is incorrect DISPATCH-547 - Stand-alone version can't download generated config file for new nodes DISPATCH-554 - Topology nodes and links are too far apart when there are a large number of routers DISPATCH-556 - qdstat fails at high scale DISPATCH-557 - High connection rates cause problems in the Python management agent DISPATCH-560 - [console] Only use the color red to indicate a failure/issue. DISPATCH-563 - Topology graph flashes and redraws a few seconds after it is 1st drawn DISPATCH-564 - Error when switching routers on Entities page DISPATCH-565 - Error fetching log on Entities page DISPATCH-566 - Message annotations are not propagated to brokers on a linkRoute DISPATCH-567 - Slight but persistent memory leak when
