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
I cannot get polling to work properly with the darcs plugin. It seems that the plugins fails to parse the change log and defaults to "Changes found" all the time (which kinda defeats the idea of polling 😄)
I have tried parsing this particular change log and I encountered 2 problems:
the log is pretty big
there is a mixture of latin-1 and utf-8 characters in the commit messages
Maybe something similar is happening here. I uploaded the full log here if you want to take a look.
Here is what I see in the polling log:
Started on Jul 26, 2013 1:32:59 AM
[workspace] $ darcs changes --repo=/srv/jenkins/jobs/gf/workspace --xml-output
[warning] Failed to get revision state for repository: /srv/jenkins/jobs/gf/workspace
[poll] Got <null> as revision state.
[workspace] $ darcs changes --repo=/srv/jenkins/jobs/gf/workspace --xml-output
[warning] Failed to get revision state for repository: /srv/jenkins/jobs/gf/workspace
[poll] Got <null> as revision state.
[poll] Last Build : #4
$ darcs changes --repo=http://www.grammaticalframework.org/ --xml-output
[warning] Failed to get revision state for repository: http://www.grammaticalframework.org/
[poll] Current remote revision is null. Local revision is hudson.scm.SCMRevisionState$None@1bbcf187.
[poll] Does not have a local revision state.
Done. Took 2.7 sec
Changes found
The text was updated successfully, but these errors were encountered:
I cannot get polling to work properly with the darcs plugin. It seems that the plugins fails to parse the change log and defaults to "Changes found" all the time (which kinda defeats the idea of polling 😄)
I have tried parsing this particular change log and I encountered 2 problems:
Maybe something similar is happening here. I uploaded the full log here if you want to take a look.
Here is what I see in the polling log:
The text was updated successfully, but these errors were encountered: