Issue #15521 has been updated by Ken Barber.
Justin ...
This was due to a stale cache ... once I cleared the cache it was fine. Because
the cache is 'cleared' upon changes only it seems, it was never flushed - which
is a concern for the environment generally (there should be a time-limit to
cache) I'll have to look into that separately.
For now the answer was:
rm -rf /opt/forge/tmp/cache/production
The tests seem to work now ... can you try again?
----------------------------------------
Refactor #15521: Move puppet module acceptance tests to the new
forge-acceptance host
https://projects.puppetlabs.com/issues/15521#change-68513
Author: Ken Barber
Status: In Topic Branch Pending Review
Priority: Normal
Assignee:
Category: module tool
Target version: 2.7.x
Affected Puppet version: 2.7.18
Keywords:
Branch:
We seem to have a real forge-acceptance host now, and it would be great if we
can start to point to it, so we can free up forge-dev for our own purposes.
Currently the forge acceptance tests require multiple points of change,
optimally if we can reduce this to 1 point of change that would be great -
ideally if we can make it configurable enough to point to our own host of
choice when required this would be even better.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
