I get a test failure on macOS:
org.apache.jmeter.protocol.http.control.DnsManagerTest >
badDnsInCustomResolverShouldFailHttpSampler(String, WireMockServer)[1]
FAILED
org.opentest4j.AssertionFailedError: HTTP is using a custom DNS
resolver, so it must fail resolving localhost
url: http://localhost:50029/index.html
response: Not Found
data.size: 84
data: No response could be served as there are no stub mappings in
this WireMock instance.
==> expected: <Non HTTP response message: Failed to resolve host
name: localhost> but was: <Not Found>
at org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:55)
at
org.junit.jupiter.api.AssertionUtils.failNotEqual(AssertionUtils.java:69)
at
org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:188)
at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1146)
at
org.apache.jmeter.protocol.http.control.DnsManagerTest.badDnsInCustomResolverShouldFailHttpSampler(DnsManagerTest.java:58)
There are quite a lot of Javadoc warnings and use of deprecated API
Also the build complains about a license violation:
> Task :src:licenses:renderLicenseForSource
Dependencies of license category B are not allowed for SOURCE artifacts
=======================================================================
CC-BY-SA-3.0
* openiconlibrary:openiconlibrary:
OFL-1.1
* font-awesome-font:font-awesome-font:4.2.0
Also the test output is quite noisy, which makes it harder to spot warnings.
I think some of the output was added to make it easier to debug CI builds.
Ideally suppress most of it except when building under a CI.
On Sat, 26 Oct 2019 at 11:00, Felix Schumacher
<[email protected]> wrote:
>
>
> Am 26.10.19 um 10:59 schrieb Milamber:
> >
> > Ok to start the RC5 today, or anyone need to add some changes?
>
> The release-plugin that generates the sha512 checksums still needs to be
> integrated.
>
> I currently try to update it from 1.34.0 to 1.36.0, but it keeps
> fighting back.
>
> Gradle doesn't complain about checksums of the plugins anymore, but the
> sha512 checksums are not generated/are in the wrong format.
>
> Felix
>
> >
> >
> >
> >
> > On 25/10/2019 13:39, Philippe Mouawad wrote:
> >> Hello,
> >>
> >> On french google group, a problem with documentation has been reported
> >>
> >> Following property logic has been changed, I’ll update doc this evening
> >> unless someone wants to do it before me:
> >>
> >> proxy.number.requests Add numeric *prefix* to Sampler names.defaults to:
> >> true
> >>
> >> Thanks
> >> proxy.number.requests Add numeric *prefix* to Sampler names.defaults to:
> >> true
> >>
> >>
> >> On Friday, October 25, 2019, sebb <[email protected]> wrote:
> >>
> >>> On Thu, 24 Oct 2019 at 23:20, Vladimir Sitnikov
> >>> <[email protected]> wrote:
> >>>> Milamber>This vote for RC4 not passed with 2 x -1 (veto) from PMC
> >>>> member.
> >>>>
> >>>> As per the ASF policy, releases may not be vetoed.
> >>> Agreed, the -1 is not a veto in the case of a release; i.e. a single
> >>> -1 does not automatically cancel the release.
> >>> However -1 votes do count towards the result, and may cause the vote to
> >>> fail.
> >>>
> >>> Also the release manager (RM) is at liberty to cancel a vote even if
> >>> there are sufficient +1 votes for it to pass.
> >>> This can happen if a problem is detected which the RM considers serious
> >>> enough.
> >>> It's not necessary for existing votes to be changed in order to
> >>> cancel the
> >>> vote.
> >>>
> >>>>> https://www.apache.org/foundation/voting.html#ReleaseVotes
> >>>>> Releases **may not** be vetoed
> >>>> Vladimir
> >>
> >
