vcsrepo module: is my patch faulty or are the test failures unjustified?

10 views
Skip to first unread message

Martin Heistermann

unread,
Apr 29, 2014, 9:45:49 AM4/29/14
to puppet...@googlegroups.com
Hi,
I have some vcsrepo resources that check out out a revision specified by SHA1 hash.
However, on every run 'git fetch' is run to verify that the correct revision is checked out.
I think that shouldn't be necessary, so I tried to patch vcsrepo to avoid such fetches in
that case:


After this change, several spec tests fail: https://gist.github.com/anonymous/11399436

You can find the source of the failing tests (current HEAD) here:

The test  "checking the revision property when its SHA1 is not different than the current
SHA should return the ref", which fits my setup, seems to fails because the changed
code does not do some git invocations required by the test, which i believe to be superfluous.

If I understand it correctly (I'm new to ruby and rspec), the other failing tests hand the string
'currentsha' to the tested code both as resource revision as well as 'git rev-parse HEAD'
output (L176, L178). I think that 'currentsha' would be the correct method return value, with no
git invocations except for 'git rev-parse HEAD'.

I am not sure if my code actually introduces wrong behavior (how?) or if the tests
failures are actually not justified and would be glad about your comments.


Thanks in advance!

Martin



Reply all
Reply to author
Forward
0 new messages