Project

General

Profile

Actions

Bug #11131

closed

Intermittent Puppet class cache test with timestamps

Added by Dominic Cleal over 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Tests
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I noticed this in the test output from #10941 just after I pushed, but it looks like we have some tests that use Time.now in the expectation and then Time.now (or new) in the tested code, so it's possible for it to run over the second boundary. This results in the following, where the timestamps are slightly different:

unexpected invocation: Proxy::Puppet::PuppetCache.write_to_cache({'./test/fixtures/modules_include' => {'testinclude' => {'timestamp' => 1436970178, 'manifest' => [[#<Proxy::Puppet::PuppetClass:0x4aac8b0>], [#<Proxy::Puppet::PuppetClass:0x4aac5b8>]]}}}, 'example_env')
unsatisfied expectations:
- expected exactly once, not yet invoked: Proxy::Puppet::PuppetCache.write_to_cache({'./test/fixtures/modules_include' => {'testinclude' => {'timestamp' => 1436970177, 'manifest' => [[#<Proxy::Puppet::PuppetClass:0x4abcb48>], [#<Proxy::Puppet::PuppetClass:0x4abca58>]]}}}, 'example_env')

Related issues 1 (0 open1 closed)

Related to Smart Proxy - Bug #10941: puppet classes cache not working rightClosed06/26/2015Actions
Actions

Also available in: Atom PDF