Gary, should we remove the fix versions for all the backlog bugs, or use a synthetic target?
I am not sure if it is worth pushing them back. Maybe only specify a concrete version if somebody
is working on it?
Gruss
Bernd
--
http://bernd.eckenfels.net
________________________________
Von: Gary D. Gregory (Jira) <jira@apache.org>
Gesendet: Saturday, October 31, 2020 3:29:00 PM
An: issues@commons.apache.org <issues@commons.apache.org>
Betreff: [jira] [Updated] (VFS-600) HttpProviderTestCase#testHttp405 is repeatedly failling
[ https://issues.apache.org/jira/browse/VFS-600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated VFS-600:
--------------------------------
Fix Version/s: (was: 2.7.0)
2.7.1
> HttpProviderTestCase#testHttp405 is repeatedly failling
> --------------------------------------------------------
>
> Key: VFS-600
> URL: https://issues.apache.org/jira/browse/VFS-600
> Project: Commons VFS
> Issue Type: Task
> Affects Versions: 2.1
> Reporter: Josh Elser
> Priority: Minor
> Fix For: 2.7.1
>
>
> testHttp405 is repeatedly failing with the below message:
> {noformat}
> testHttp405(org.apache.commons.vfs2.provider.http.test.HttpProviderTestCase) Time elapsed:
0.558 sec <<< ERROR!
> org.apache.commons.vfs2.FileSystemException: Could not determine the size of "http://www.w3schools.com/webservices/tempconvert.asmx?action=WSDL"
because it is not a file.
> at org.apache.commons.vfs2.provider.DefaultFileContent.getSize(DefaultFileContent.java:135)
> at org.apache.commons.vfs2.provider.http.test.HttpProviderTestCase.testHttp405(HttpProviderTestCase.java:208)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.commons.vfs2.test.AbstractProviderTestCase.runTest(AbstractProviderTestCase.java:218)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:252)
> at junit.framework.TestSuite.run(TestSuite.java:247)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
> at org.apache.commons.vfs2.test.AbstractTestSuite$1.protect(AbstractTestSuite.java:149)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at org.apache.commons.vfs2.test.AbstractTestSuite.run(AbstractTestSuite.java:154)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {noformat}
> It seems like that URL is now throwing an HTTP 404?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
|