Bug 12626 - [master] BitbakeSelftest failed mtd-utils.git check
Summary: [master] BitbakeSelftest failed mtd-utils.git check
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.5
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Ross Burton
QA Contact:
URL: https://autobuilder.yocto.io/builders...
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-03-25 07:39 UTC by Armin Kuster
Modified: 2018-03-26 02:51 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Armin Kuster 2018-03-25 07:39:22 UTC 
.....................................................................................................................................................................................................................................F........................................................................................................
======================================================================
FAIL: test_git_latest_versionstring (bb.tests.fetch.FetchLatestVersionTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/pokybuild/yocto-autobuilder/yocto-worker/nightly/build/bitbake/lib/bb/tests/fetch.py", line 916, in test_git_latest_versionstring
    self.assertTrue(verstring, msg="Could not find upstream version")
AssertionError: '' is not true : Could not find upstream version

Stdout:
Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 ls-remote git://git.yoctoproject.org/poky refs/tags/*
Running export PSEUDO_DISABLED=1; git -c core.fsyncobjectfiles=0 ls-remote git://git.yoctoproject.org/poky refs/tags/*
Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 ls-remote git://git.gnome.org/mobile-broadband-provider-info refs/tags/*
Running export PSEUDO_DISABLED=1; git -c core.fsyncobjectfiles=0 ls-remote git://git.gnome.org/mobile-broadband-provider-info refs/tags/*
Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 ls-remote git://github.com/kergoth/chkconfig refs/tags/*
Running export PSEUDO_DISABLED=1; git -c core.fsyncobjectfiles=0 ls-remote git://github.com/kergoth/chkconfig refs/tags/*
Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 ls-remote git://anongit.freedesktop.org/git/xorg/proto/presentproto refs/tags/*
Running export PSEUDO_DISABLED=1; git -c core.fsyncobjectfiles=0 ls-remote git://anongit.freedesktop.org/git/xorg/proto/presentproto refs/tags/*
Fetcher accessed the network with the command git -c core.fsyncobjectfiles=0 ls-remote git://git.infradead.org/mtd-utils.git refs/tags/*
Running export PSEUDO_DISABLED=1; git -c core.fsyncobjectfiles=0 ls-remote git://git.infradead.org/mtd-utils.git refs/tags/*

----------------------------------------------------------------------
Ran 334 tests in 241.495s

FAILED (failures=1)
Comment 1 Armin Kuster 2018-03-25 07:40:25 UTC 
manual check failed too

git -c core.fsyncobjectfiles=0 ls-remote git://git.infradead.org/mtd-utils.git refs/tags/*
fatal: unable to connect to git.infradead.org:
git.infradead.org[0: 2607:7c80:54:e::133]: errno=No route to host
git.infradead.org[1: 198.137.202.133]: errno=Connection timed out

Maybe its down ?  Can we not fail the entire test because one url failed?
Comment 2 Ross Burton 2018-03-26 02:51:23 UTC 
$ git -c core.fsyncobjectfiles=0 ls-remote git://git.infradead.org/mtd-utils.git
80de29a464c7ed639ae337860b5fb346fde8abe5	HEAD
ca39eb1d98e736109c64ff9c1aa2a6ecca222d8f	refs/heads/fastmap
80de29a464c7ed639ae337860b5fb346fde8abe5	refs/heads/master
7afca4241e082c23bb38a4da532cc222457ae719	refs/heads/origin
7ddeed0c79a524f222d2911c023781c88f63eaf7	refs/tags/v1.0.0
3b4b1a09d0f0a753dc46b4f2f97200300010587b	refs/tags/v1.1.0
230b13b2d9b109b5c166b4b0334609b52b452d12	refs/tags/v1.2.0
58d2ccb55262ee1f88cbcb5aec0d762ba784fb2c	refs/tags/v1.3.0
a4e502d99129da8ebba6d40b373a4422a175e9af	refs/tags/v1.3.0^{}
0aaa1030ab88273b1e5fa7eb630abdb1bbc85a3e	refs/tags/v1.3.1
a67747b7a314e685085b62e8239442ea54959dbc	refs/tags/v1.3.1^{}
c9bdc0ca41b8ca9658d6ec7e22b2fd708a450b67	refs/tags/v1.4.0
3c3674a6e1d3f59554b0ff68ca59be2fd4134e0c	refs/tags/v1.4.1
70f86090720d7b5b8203ee43356f8c6f79219896	refs/tags/v1.4.2
0a63610bbcdfa2c75d0637e542d1ab67704e34de	refs/tags/v1.4.3
b22f7f386ba37a766aedd8e8cf34781a3d1daad2	refs/tags/v1.4.4
5319b84974fcb71504aed2d1b8285e9c0a4a4bb8	refs/tags/v1.4.5
baafd8ace3301e9d2ba314a376bad008314b34ff	refs/tags/v1.4.6
f8aa6922dde02835ba97e84be41f387cdd38ec7d	refs/tags/v1.4.7
d37fcc0afd0d4a14c56812847e8e4257d0a99e3b	refs/tags/v1.4.8
3cf9c62fdb5cf41098e3ab2265c2d370a821ad98	refs/tags/v1.4.9
995cfe51b0a3cf32f381c140bf72b21bf91cef1b	refs/tags/v1.4.9^{}
b0f3b6ea464f7cf97d430762c9491e20da0875be	refs/tags/v1.5.0
ca39eb1d98e736109c64ff9c1aa2a6ecca222d8f	refs/tags/v1.5.0^{}
9dec4621e33db1df07730158ed2c8f884af5a6a3	refs/tags/v1.5.1
9f107132a6a073cce37434ca9cda6917dd8d866b	refs/tags/v1.5.1^{}
ea3c6f04fddf19a1b76b073d463f08b5d8ca5890	refs/tags/v1.5.2
aea36417067dade75192bafa03af70b6eb2677b1	refs/tags/v1.5.2^{}
256d4237ae743c7ddf2cea0dee1c4279cf368a7a	refs/tags/v2.0.0
1bfee8660131fca7a18f68e9548a18ca6b3378a0	refs/tags/v2.0.0^{}
e3d3b5d8966143b4281b88e54bc34740ddc70877	refs/tags/v2.0.0-rc1
abbed09157dc42f11d54277ad895edaf357d92d8	refs/tags/v2.0.0-rc1^{}
ebbe9c8a50730fae205a84853ace7a3f1e063680	refs/tags/v2.0.0-rc2
55dd808e71cb7e080a2643e0302321f4a1f699d3	refs/tags/v2.0.0-rc2^{}
b19b57f165cecb892c406636683eb0d257639dcb	refs/tags/v2.0.1
81049e599775bac4238361752f659a86f67328e6	refs/tags/v2.0.1^{}

I'm guessing the machine was down for a bit.