In this case trigger the CI build manually. There might be erronous tests blocking a port, as you say, if they use same ports. Thx
On Thu, Jun 13, 2019 at 6:57 PM Michael Osipov <micha...@apache.org> wrote: > Am 2019-06-13 um 18:45 schrieb Tibor Digana: > > Hi Michael, > > > > The latest build failed [1]. Have you analysed the root cause with these > > failed tests? > > [1]: > > > https://builds.apache.org/job/maven-box/job/maven-wagon/job/master/16/#showFailuresLink > > Take a closer look at them, it is either a Windows file locking issue or > zombie process blocking a port. > > > On Thu, Jun 13, 2019 at 3:46 PM Michael Osipov <micha...@apache.org> > wrote: > > > >> Hi, > >> > >> We solved 6 issues: > >> > >> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&version=12345501 > >> > >> There are still a couple of issues left in JIRA: > >> > >> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20WAGON%20AND%20resolution%20%3D%20Unresolved > >> > >> Staging repo: > >> https://repository.apache.org/content/repositories/maven-1514/ > >> > >> > https://repository.apache.org/content/repositories/maven-1514/org/apache/maven/wagon/wagon/3.3.3/wagon-3.3.3-source-release.zip > >> > >> Source release checksum(s): > >> wagon-3.3.3-source-release.zip > >> sha512: > >> > >> > 3fae2bea760a03896df395cee1896aa4a02e031fdc86daaba781243cad9aefa1c1c99fc7daa95e04da0248e5aa7649511d08503807dad5fc92d80e25202c999e > >> > >> Staging site: > >> https://maven.apache.org/wagon-archives/wagon-LATEST/ > >> > >> Guide to testing staged releases: > >> https://maven.apache.org/guides/development/guide-testing-releases.html > >> > >> Vote open for 72 hours. > >> > >> [ ] +1 > >> [ ] +0 > >> [ ] -1 > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > >> For additional commands, e-mail: dev-h...@maven.apache.org > >> > >> > > > >
