[
https://issues.apache.org/jira/browse/CLIMATE-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15617795#comment-15617795
]
ASF GitHub Bot commented on CLIMATE-889:
----------------------------------------
Github user agoodm commented on the issue:
https://github.com/apache/climate/pull/419
Right... but that does not mean there will be inherently nothing wrong with
the rest of the test, since having access to these datasets is a prerequisite.
What would we do then if we eventually make changes to the dap loader that have
some sort of bugs, but don't notice them because the opendap test server is
down as it is now and the tests falsely pass? I get that it is annoying to have
constant build failures that aren't our fault, but at the very least I can is
that the failures at least force you to investigate the logs. Conversely I fear
that this would lead to us being less likely to check the build logs in the
scenario I mention above since if you don't, you'd have know way of knowing
that those tests were actually skipped.
> Fix Travis Build
> ----------------
>
> Key: CLIMATE-889
> URL: https://issues.apache.org/jira/browse/CLIMATE-889
> Project: Apache Open Climate Workbench
> Issue Type: Bug
> Reporter: Ibrahim Jarif
> Assignee: Ibrahim Jarif
> Fix For: 1.2.0
>
>
> The travis build is failing due to 2 tests
> 1. TestDap - The openDap urls fails to load at times.
> 2. TestPodaac - The url used to fetch the dataset isn't working (HTTP 403
> exception)
> The simplest fix is to skip these tests if an exception occurs during
> downloading of the datasets.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
