buildbot failures on Windows
Simon Heimberg
simohe at besonet.ch
Sat Nov 9 14:44:17 CST 2013
Buildbot running on windows has 20 failing Tests, but the reasons are
only a few.
Here is my analysis (of build 42 to 46, which are all the same):
build 46:
http://hgbuildbot.kublai.com/builders/Windows%202008%20R2%20hg%20tests/builds/46/steps/run-tests.py%20%28python2.6%29
Failed test-largefiles.t: output changed
encoded path (\ is encoded)
missing glob
Failed test-extension.t: output changed
import problems
missing glob
Failed test-phases-exchange.t: output changed
server start problem
Failed test-transplant.t: output changed
server start problem
Failed test-mq-subrepo.t: output changed
missing glob
Failed test-treediscovery.t: output changed and returned error code 1
server start problem
Failed test-lfconvert.t: output changed
encoded path (\ is encoded)
Failed test-wireproto.t: output changed
server start problem
Failed test-treediscovery-legacy.t: output changed
server start problem
Failed test-mq-qimport.t: output changed
server start problem
Failed test-push-http.t: output changed
server start problem
Failed test-mq-qclone-http.t: output changed
server start problem
Failed test-import-merge.t: output changed
hunk fail instead of succeed
Failed test-largefiles-cache.t: output changed
encoded path (\ is encoded)
Failed test-http-branchmap.t: output changed
server start problem
Failed test-subrepo-relative-path.t: output changed
server start problem
Failed test-share.t: output changed
server start problem
Failed test-pull-http.t: output changed
server start problem
Failed test-known.t: output changed
server start problem
Failed test-unbundlehash.t: output changed
server start problem
More information about the Mercurial-devel
mailing list