You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.
It looks like the class not documented error has swapped places with the does_not::exist not in autoload module layout error, which looks to make some sense as it comes before the other.
The text was updated successfully, but these errors were encountered:
Uncommonly puppet-lint changes the ordering of messages. This also seems to be tied to environments somehow, as the ordering on my workstations syncs with appveyor and travis-ci here, but not travis-ci on another project or circle-ci here. When this happens, I just rerun the CI and then it usually passes.
If anything this is a bug in puppet-lint, but having messages in a specific order is not really going to be high on a priority list.
Uncommonly puppet-lint changes the ordering of messages.
Oh, lovely. Good to know!
If anything this is a bug in puppet-lint, but having messages in a specific order is not really going to be high on a priority list.
If puppet-lint doesn't provide a way to request ordered results there is nothing we can do about that here. We might rewrite the tests to simply look for messages with those contents, instead of the exact order they are coming in as.
As an example of somewhere else this occurs, my puppet-lint parsing test at puppet-check always has that order specified in the regular expression on the travis-ci matrix, but always has the reverse order on my laptop.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We've got a failing build on
master
from #155.It looks like the
class not documented
error has swapped places with thedoes_not::exist not in autoload module layout
error, which looks to make some sense as it comes before the other.The text was updated successfully, but these errors were encountered: