Just want to confirm, your FreeBSD and build.apache.org's ubuntu see the same test failure??
Do you think we should cancel the vote and wait for your fix? Thanks -Dan On Sun, Dec 25, 2016 at 10:34 AM, Michael Osipov <micha...@apache.org> wrote: > Am 2016-12-25 um 18:45 schrieb Dan Tran: > >> Thank Michael >> >> * Test failures at windows are intermittent. It is a known issue since >> the last few versions >> * No issue at my local redhat 7/java7 build >> * I am seeing test failures at >> https://builds.apache.org/view/All/job/maven-wagon/1323/ starting with >> your change for WAGON-472. Dont think it is related, could be from build >> env >> > > This is build env. I have tested Wagon on Windows and FreeBSD before any > patching. Windows was fine, FreeBSD failed for those two cases. It also > passed on Windows with OpenJDK 7 Update 121 from Azul Systems. Though, I > have good news: I have been working on the unit tests in genereal the last > two days by migrating to Jetty 8 (last Java 1.6 supported) version and > found several bugs in Wagon HTTP Provider and the unit test setup itself. I > will report them shortly. > > Michael > > > On Sat, Dec 24, 2016 at 5:07 AM, Michael Osipov <micha...@apache.org> >> wrote: >> >> Am 2016-12-24 um 04:07 schrieb Dan Tran: >>> >>> Hi, >>>> >>>> We have fixed 18 issues: >>>> *https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj >>>> ectId=12318122&version=12333396 >>>> <https://issues.apache.org/jira/secure/ReleaseNote.jspa?proj >>>> ectId=12318122&version=12333396>* >>>> >>>> There are still issues left in JIRA: >>>> *https://issues.apache.org/jira/issues/?jql=project%20%3D% >>>> 20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY% >>>> 20created%20DESC%2C%20priority%20DESC >>>> <https://issues.apache.org/jira/issues/?jql=project%20%3D% >>>> 20WAGON%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY% >>>> 20created%20DESC%2C%20priority%20DESC>* >>>> >>>> Staging repository: >>>> https://repository.apache.org/content/repositories/maven-1313 >>>> https://repository.apache.org/content/repositories/maven- >>>> 1313/org/apache/maven/wagon/wagon/2.11/wagon-2.11-source-release.zip >>>> >>>> Source release checksum(s): >>>> wagon-2.11-source-release.zip sha1: 98bc0b031880b175e144c55447a620 >>>> 00c58abfa5 >>>> >>>> Staging site: >>>> *http://maven.apache.org/components/wagon-archives/wagon-LATEST/ >>>> <http://maven.apache.org/components/wagon-archives/wagon-LATEST/>* >>>> >>>> Guide to testing staged releases: >>>> https://maven.apache.org/guides/development/guide-testing-releases.html >>>> <https://maven.apache.org/guides/development/guide-testing- >>>> releases.html> >>>> Vote open for 72H + 48H to accomodate for holidays >>>> >>>> >>> +1 >>> >>> SHA1 is fine, site is fine. Builds passes on Windows but constantly fails >>> on non-Windows, here on my FreeBSD machine as well as on our Jenkins >>> Ubuntu >>> slave. It should probably investigated for the 3.0 release. >>> >>> Michael >>> >>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >>> For additional commands, e-mail: dev-h...@maven.apache.org >>> >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
