{"thread":{"id":"22639","subject":"t7400.24 git submodule 'update --init' test fails on some machines","startedAt":"2010-02-13T09:05:45Z","lastAt":"2010-02-17T10:23:16Z","messageCount":2,"participants":["Jonathan Nieder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"134415","messageId":"20100213090544.GA29850@progeny.tock","threadId":"22639","inReplyTo":null,"subject":"t7400.24 git submodule 'update --init' test fails on some machines","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2010-02-13T09:05:45Z","receivedAt":"2010-02-13T09:05:45Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Some machines I don’t have access to have been hitting a test failure\nwhen building git 1.6.6.2 and 1.7.0-rc2.  I am looking for ideas.\n\nThe failed test is #24 from t7400-submodule-basic.sh:\n\n test_expect_success 'update --init' '\n\n\tmv init init2 &&\n\tgit config -f .gitmodules submodule.example.url \"$(pwd)/init2\" &&\n\tgit config --remove-section submodule.example\n\tgit submodule update init > update.out &&\n\tgrep \"not initialized\" update.out &&\n\ttest ! -d init/.git &&\n\tgit submodule update --init init &&\n\ttest -d init/.git\n\n '\n\nThat is supposed to produce output like\n\n| Submodule path 'init' not initialized\n| Submodule 'example' (<top>/t/trash directory.t7400-submodule-basic/init2) registered for path 'init'\n| Initialized empty Git repository in <top>/t/trash directory.t7400-submodule-basic/init/.git/\n| Submodule path 'init': checked out 'OBJID'\n| *   ok 24: update --init\n\nbut instead it just produces\n\n| * FAIL 24: update --init\n\nThe silence suggests that the ‘git submodule update init’ command does\nnot perceive the submodule not to be initialized, or in other words,\nthat one of the earlier ‘git config’ commands is failing.\n\nNone of the earlier tests fail, and none of the other t7400 tests\nfail.\n\nRecent results for the ‘update --init’ test (note that even for the\nsame arch, different builds are usually on different machines):\n\nresult\tgit\t\tarch\tlibc\t\tlog\nok\t1.6.6.1\t\ti386\t2.10.2-5\t[1]\nok\t1.6.6.1\t\ts390\t2.10.2-5\t[2]\nok\t1.6.6.1\t\tia64\t2.10.2-5\t[3]\nok\t1.6.6.1\t\thppa\t2.10.2-5\t[4]\nok\t1.6.6.2\t\ti386\t2.10.2-5\t[5]\nok\t1.6.6.2\t\ts390\t2.10.2-6\t[6]\nFAIL\t1.6.6.2\t\tia64\t2.10.2-6\t[7]\nFAIL\t1.6.6.2\t\thppa\t2.10.2-5\t[8]\nok\t1.7.0-rc2\ti386\t2.10.2-6\t[9]\nFAIL\t1.7.0-rc2\ts390\t2.10.2-6\t[10]\n\nThe two s390’s are particularly strange.  Same kernel image, same\nlibc, different machines, different results.\n\nUnfortunately, the logs with “ok” (except for ia64 1.6.6.1) do\nnot include “make test GIT_TEST_OPTS=-v” output.\n\nJohan, from staring at the code, I don’t think commit 65807ee\n(builtin-config: Fix crash when using \"-f <relative path>\" from\nnon-root dir, 2010-01-26) would have anything to do with this, but\nnothing else related has changed recently so I CCed you anyway.\n\nIt is hard to blame git for something so architecture-dependent\nand inconsistent, but one has to start somewhere.\n\nThoughts?\nJonathan\n\n[1] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.6.6.1-1&arch=i386&stamp=1264681049&file=log\n[2] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.6.6.1-1&arch=s390&stamp=1264681505&file=log\n[3] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.6.6.1-1&arch=ia64&stamp=1264690704&file=log\n[4] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.6.6.1-1&arch=hppa&stamp=1264695557&file=log\n[5] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.6.6.2-1&arch=i386&stamp=1265992804&file=log\n[6] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.6.6.2-1&arch=s390&stamp=1265994666&file=log\n[7] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.6.6.2-1&arch=ia64&stamp=1265994466&file=log\n[8] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.6.6.2-1&arch=hppa&stamp=1266038878&file=log\n[9] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.7.0~rc2-1&arch=i386&stamp=1265996497&file=log\n[10] https://buildd.debian.org/fetch.cgi?&pkg=git-core&ver=1:1.7.0~rc2-1&arch=s390&stamp=1266025527&file=log\n\nRecent point release builds:\nhttps://buildd.debian.org/status/package.php?p=git-core\n\nAll builds:\nhttps://buildd.debian.org/build.php?arch=&pkg=git-core\n"},{"id":"134857","messageId":"20100217102315.GA6364@progeny.tock","threadId":"22639","inReplyTo":"20100213090544.GA29850@progeny.tock","subject":"Re: t7400.24 git submodule 'update --init' test fails on some machines","fromName":"Jonathan Nieder","fromEmail":"jrnieder@gmail.com","sentAt":"2010-02-17T10:23:16Z","receivedAt":"2010-02-17T10:23:16Z","isPatch":false,"sender":{"key":"jrnieder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/281595?v=4"},"body":"Jonathan Nieder wrote:\n> Some machines I don’t have access to have been hitting a test failure\n> when building git 1.6.6.2 and 1.7.0-rc2.  I am looking for ideas.\n> \n> The failed test is #24 from t7400-submodule-basic.sh:\n> \n>  test_expect_success 'update --init' '\n\nLooks like it was an infrastructure problem of some kind.  I still\nhaven’t figured it out what changed, but all the affected platforms\ndealt fine with 1.7.0.  There was no need to bother you.\n\nSo sorry for the noise,\nJonathan\nhttps://buildd.debian.org/status/package.php?p=git-core - build logs\n"}]}