Hi Syd,

I had that problem the other week with some otherwise benign changes where I mentioned "Error in listObject Example" (26 October) https://github.com/TEIC/TEI/commits you'll see immediately after I committed "inconsequential commit to trick Jenkins".

This is because the way Jenkins flags whether there is an error or not is parsing the console output for the word 'error'. Imagine how fun this would be if one of our tests returned "No errors here!". Sigh. So having it do it again won't do anything but find the same error it thinks exists because your commit message is present.

I'd suggest, if you haven't already, just making a trivial change, even just spacing, and re-committing/pushing without mentioning the word 'error'. ;-)

Best wishes,

James

Dr James Cummings, James.Cummings@newcastle.ac.uk
Senior Lecturer in Late-Medieval Literature and Digital Humanities

School of English, Newcastle University

Could the Jenkins maintainers force the Stylesheets-dev job to
re-build?

My check-in from this morning's meeting built as well as can be
expected on my local system. It fails in Jenkins, flagging my commit
message itself (which contains the word "error"). I'm hoping that if
Mr. Jenkins just does the work again, it will work. If not, I'll try
committing some tiny tweak with a different commit message.
_______________________________________________
Tei-council mailing list
Tei-council@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council