Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6567

Test failure: /spec/unit/face/generate_spec.rb:149

    XMLWordPrintable

    Details

    • Type: CI Blocker
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.6.0
    • Component/s: None
    • Labels:
      None
    • CI Pipeline/s:
      platform legacy Puppet
    • Story Points:
      1
    • Sprint:
      Language 2016-08-10
    • Release Notes:
      Not Needed
    • Release Notes Summary:
      problem introduced and fixed before release

      Description

      From Jenkins:

      04:26:21 Failures:
      04:26:21 
      04:26:21   1) Puppet::Face[:generate, v0.1.0] when used from an interactive terminal in an environment with two modules containing resource types creates output with matching names for each input
      04:26:21      Failure/Error: expect(children).to eql(['test1.pp', 'test2.pp'])
      04:26:21        
      04:26:21        expected: ["test1.pp", "test2.pp"]
      04:26:21             got: ["test2.pp", "test1.pp"]
      04:26:21        
      04:26:21        (compared using eql?)
      04:26:21      # ./spec/unit/face/generate_spec.rb:153:in `block (4 levels) in <top (required)>'
      04:26:21      # ./spec/unit/face/generate_spec.rb:111:in `block (6 levels) in <top (required)>'
      04:26:21      # ./lib/puppet/context.rb:65:in `override'
      04:26:21      # ./lib/puppet.rb:240:in `override'
      04:26:21      # ./spec/unit/face/generate_spec.rb:110:in `block (5 levels) in <top (required)>'
      04:26:21      # ./lib/puppet/context.rb:65:in `override'
      04:26:21      # ./lib/puppet.rb:240:in `override'
      04:26:21      # ./spec/unit/face/generate_spec.rb:109:in `block (4 levels) in <top (required)>'
      04:26:21 

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            hailee Hailee Kenney
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support