GitHub user wilderrodrigues opened a pull request:

    https://github.com/apache/cloudstack/pull/616

    CLOUDSTACK-8660 - StringUtilsTest.testGetPrefferedCharset() fails because 
the preferred charset is not always UTF-8

    Test was failing due to "expected:<UTF-8> but was:<US-ASCII>"
    
    Build is successful:
    
    [INFO] BUILD SUCCESS
    [INFO] 
------------------------------------------------------------------------
    [INFO] Total time: 11:24 min
    [INFO] Finished at: 2015-07-22T13:51:49+02:00
    [INFO] Final Memory: 114M/927M
    [INFO] 
------------------------------------------------------------------------
    
    Test report for test_vm_life_cycle will be sent  in a bit.
    
    @DaanHoogland @bhaisaab , could you please have a look at that?
    
    Cheers,
    Wilder

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/schubergphilis/cloudstack 
fix/string_utils_test

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/616.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #616
    
----
commit a45268f2b2e43a5fb27bdc5b5a643a9abfcef84a
Author: wilderrodrigues <wrodrig...@schubergphilis.com>
Date:   2015-07-22T11:24:44Z

    CLOUDSTACK-8660 - Formatting test and utility classes

commit c6057961bc808a344f2858233598044cc9e4012c
Author: wilderrodrigues <wrodrig...@schubergphilis.com>
Date:   2015-07-22T11:37:43Z

    CLOUDSTACK-8660 - Adding a method to check if UTF-8 is supported
    
       - Changing the test to call isUtf8Supported() before checking if the 
preferred charset is actually UTF-8

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to