Steps to reproduce: $ . oe-init-build-env;bitbake-selftest Expected outcome: All test must pass Current outcome (full log attached): ====================================================================== ERROR: test_git_latest_versionstring (bb.tests.fetch.FetchLatestVersionTest) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/lsandov1/poky/bitbake/lib/bb/tests/fetch.py", line 751, in test_git_latest_versionstring pupver= ud.method.latest_versionstring(ud, self.d) File "/home/lsandov1/poky/bitbake/lib/bb/fetch2/git.py", line 369, in latest_versionstring output = self._lsremote(ud, d, "refs/tags/*") File "/home/lsandov1/poky/bitbake/lib/bb/fetch2/git.py", line 335, in _lsremote output = runfetchcmd(cmd, d, True) File "/home/lsandov1/poky/bitbake/lib/bb/fetch2/__init__.py", line 817, in runfetchcmd val = d.getVar(var, True) or d.getVar("BB_ORIGENV", False).getVar(var, True) AttributeError: 'NoneType' object has no attribute 'getVar' Build description: commit f7b520878babbaa7527151f22c031ae160512753 Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Fri Apr 29 07:40:56 2016 +0100 poky: Switch to post release name/version (From meta-yocto rev: c9766c66525a0c1b040d1282ecc1c6f41c615dc7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> MACHINE ??= "qemux86" AU page: https://autobuilder.yoctoproject.org/main/builders/nightly/builds/828
Created attachment 3166 [details] Log produced when running bitbake-selftest.
Fixed in bitbake f368f5ae64a1681873f3d81f3cb8fb38650367b0.
This is working as expected now: Validated on commit 7b9e1f5ad8a427356f2ec516b1718138a7d3c64e ********************************************** bitbake-selftest .......................................................................................................................................................... ---------------------------------------------------------------------- Ran 154 tests in 120.713s OK *******************************************
Krogoth has the same failure. I reproduced using the current release and with krogoth-next I am preparing for pull request. AU https://autobuilder.yoctoproject.org/main/builders/nightly/builds/917. This fix should be back ported to krogoth but it is not clear exactly were. Should this bug be re-opened or a new one for krogoth? - Armin
I back ported this fix for Krogoth and is appears to fix the problem there too.