Uploaded image for project: 'Beaker'
  1. Beaker
  2. BKR-42

Beaker Fails to Run Tests that Contain Unicode

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Trivial
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      PE Version: 3.3.0-rc1-127-gfc2cc6c
      ACL Module Commit: 9d2f0b4124254c84581e379ab80308e6a0f239bf
      Master: 1GB RAM - CentOS 6.4 x64
      Agent: 2GB RAM - Windows 2008 R2 x64

    • Template:
    • Epic Link:
    • Team:
      Quality Engineering
    • Story Points:
      3

      Description

      Description

      If a user attempts to use Unicode inside inline manifests for Beaker tests the test will fail with the error message:

      #<Encoding::CompatibilityError: incompatible character encodings: ASCII-8BIT and UTF-8>
      

      Attachments

      • Beaker Test
      • Beaker Config
      • Beaker Command Script
      • Beaker Logs

      Repro Steps

      1. Install Puppet Enterprise onto master node.
      2. Install Puppet Enterprise onto a Windows agent node.
      3. Download the Beaker test artifacts locally.
      4. Execute the included command-line script:

        ./command_local.sh

      Expect

      Beaker should execute the test without issue.

      Actual

      Beaker fails with the error message:

      #<Encoding::CompatibilityError: incompatible character encodings: ASCII-8BIT and UTF-8>
      

        Attachments

        1. add_perms_to_unicode_dir.rb
          1 kB
        2. command_local.sh
          0.4 kB
        3. pe_install.rb
          0.4 kB
        4. tests-run.log
          6 kB
        5. windows-local.cfg
          0.3 kB

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ryan.gard Ryan Gard
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support