[Rt-commit] rt branch, 3.9-trunk, updated. rt-3.8.8-825-g07448f2

[? sunnavy]

The branch, 3.9-trunk has been updated
       via  07448f26708fb3715d556218c4ed8f80591a4ea3 (commit)
      from  061cdbb16cbe64c9a0b10429065e6460ab8912aa (commit)

Summary of changes:
 t/mail/wrong_mime_charset.t |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

- Log -----------------------------------------------------------------
commit 07448f26708fb3715d556218c4ed8f80591a4ea3
Author: sunnavy <sunnavy at bestpractical.com>
Date:   Mon Sep 20 13:15:36 2010 +0800

    we encode twice, so there are 2 warnings

diff --git a/t/mail/wrong_mime_charset.t b/t/mail/wrong_mime_charset.t
index 47638ef..ca94b16 100644
--- a/t/mail/wrong_mime_charset.t
+++ b/t/mail/wrong_mime_charset.t
@@ -18,7 +18,9 @@ my $mime           = MIME::Entity->build(
 $mime->head->mime_attr( "Content-Type.charset" => 'utf8' );
 warnings_are {
     RT::I18N::SetMIMEEntityToEncoding( $mime, 'iso-8859-1' );
-} ['Encoding error: "\x{fffd}" does not map to iso-8859-1'], " We can't encode something into the wrong encoding without Encode complaining";
+}
+[ ('Encoding error: "\x{fffd}" does not map to iso-8859-1') x 2, ],
+" We can't encode something into the wrong encoding without Encode complaining";
 
 
 my $subject = decode( 'iso-8859-1', $mime->head->get('Subject') );

-----------------------------------------------------------------------