jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCLOUDS-778) Remove OS support tests from TemplateBuilderLiveTest, as people are ignoring failures
Date Tue, 18 Nov 2014 17:53:35 GMT

    [ https://issues.apache.org/jira/browse/JCLOUDS-778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14216512#comment-14216512
] 

ASF subversion and git services commented on JCLOUDS-778:
---------------------------------------------------------

Commit aec64012ee5cc1a295e9490ddb5a70dd9b9eee16 in jclouds's branch refs/heads/1.7.x from
[~adrian.f.cole@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=aec6401 ]

JCLOUDS-778 Remove OS support tests from TemplateBuilderLiveTest, as people are ignoring failures,


> Remove OS support tests from TemplateBuilderLiveTest, as people are ignoring failures
> -------------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-778
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-778
>             Project: jclouds
>          Issue Type: Task
>          Components: jclouds-core
>            Reporter: Adrian Cole
>             Fix For: 1.8.2, 1.9.0, 1.7.4
>
>
> Developers don't seem to be running live tests much anymore. Prime example is even amazon
ec2 is now rusting! JCLOUDS-775
> Part of this is likely that they fail for trivial reasons due to a somewhat obsessive
test approach I introduced many years ago. Basically, we defined the "supported operating
system" list in subtypes of BaseTemplateBuilderLiveTest. We once thought that we would test
multiple os families, but we've never done that. In the mean time, the supported operating
system part of the test is just something that breaks every 3 months when a provider adds
or removes an OS version. Since there's no action we can take on that, and this drowns out
real issues in the provider, let's remove it.
> What we retain are more important aspects, such as properties apply, or that the default
template resolves to known values. Since all our tests work off the resolved template, we
do need to be aware when that changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message