Analyse following RPM build log snippet. Describe contents accurately, without speculation or suggestions for resolution.            
Your analysis must be as concise as possible, while keeping relevant information intact.
Snippet: 
  1) ABRT #handle_exception logs error into syslog when can't communicate with ABRT daemon because no-one is listeing on the other side
     Failure/Error: expect(syslog).to receive(:err).with("%s", /can't communicate with ABRT daemon, is it running\? Connection refused -( connect\(2\) for)? "?#{socket_path}"?/)
       #<Double "syslog"> received :err with unexpected arguments
         expected: ("%s", /can't communicate with ABRT daemon, is it running\? Connection refused -( connect\(2\) for)? "?\/bui...ygem-abrt-0.4.0-build\/abrt-0.4.0\/usr\/share\/gems\/gems\/abrt-0.4.0\/spec\/abrt_handler_spec.rb"?/)
              got: ("%s", "can't communicate with ABRT daemon, is it running? too long unix socket path (114bytes given but 108bytes max)")
       Diff:
       @@ -1,3 +1,3 @@
        ["%s",
       - /can't communicate with ABRT daemon, is it running\? Connection refused -( connect\(2\) for)? "?\/builddir\/build\/BUILD\/rubygem-abrt-0.4.0-build\/abrt-0.4.0\/usr\/share\/gems\/gems\/abrt-0.4.0\/spec\/abrt_handler_spec.rb"?/]
       + "can't communicate with ABRT daemon, is it running? too long unix socket path (114bytes given but 108bytes max)"]
     # ./spec/abrt_handler_spec.rb:140:in 'block (5 levels) in <top (required)>'

Test suite error. The interesting bit is the `too long unix socket path (114bytes given but 108bytes max)` part, which suggests that the paths has bigger nesting then expected. This was actually triggered by changes in RPM build directory structure.