There was 2 regression for autopkgtest, I was able to make the amd64 pass after 4 attempts. After 5 attempts for i386, it still fails.
The failure as nothing to do with the uploaded patch. It's seems to be a network glitch during the autopkgtest. I guess it will succeed eventually at restarting the test over and over again just like it did for 'amd64'.
Other architecture (arm64,ppc64el) set to 'Always failed' fails the exact same way. Last one it succeeded was with kernel 4.15.0-20[3]
[1] buildlogs
Network lxdbr0 created
Storage pool default created
Device root added to default
Creating autopkgtest-prepare-3fF
Error: Failed container creation: Get https://images.linuxcontainers.org/streams/v1/index.json: Unable to connect to: images.linuxcontainers.org:443
Error: not found
[2] buildlogs
Building for 4.15.0-22-generic
Building for architecture i686
Building initial module for 4.15.0-22-generic
Error! Build of dahdi_vpmadt032_loader.ko failed for: 4.15.0-22-generic (i686)
Consult the make.log in the build directory
== Cosmic : excuse page regression ==
# From excuses... page
* autopkgtest for autopkgtest/5.3.1: amd64: Pass, arm64: Pass, armhf: Pass, i386: Regression ♻ , ppc64el: Pass, s390x: Pass[1]
There was 2 regression for autopkgtest, I was able to make the amd64 pass after 4 attempts. After 5 attempts for i386, it still fails.
The failure as nothing to do with the uploaded patch. It's seems to be a network glitch during the autopkgtest. I guess it will succeed eventually at restarting the test over and over again just like it did for 'amd64'.
* autopkgtest for dahdi-linux/ 1:2.11. 1~dfsg- 1ubuntu4: amd64: Pass, arm64: Always failed, armhf: Pass, i386: Regression ♻ , ppc64el: Always failed, s390x: Ignored failure[2]
Other architecture (arm64,ppc64el) set to 'Always failed' fails the exact same way. Last one it succeeded was with kernel 4.15.0-20[3]
[1] buildlogs prepare- 3fF /images. linuxcontainers .org/streams/ v1/index. json: Unable to connect to: images. linuxcontainers .org:443
Network lxdbr0 created
Storage pool default created
Device root added to default
Creating autopkgtest-
Error: Failed container creation: Get https:/
Error: not found
[2] buildlogs _loader. ko failed for: 4.15.0-22-generic (i686)
Building for 4.15.0-22-generic
Building for architecture i686
Building initial module for 4.15.0-22-generic
Error! Build of dahdi_vpmadt032
Consult the make.log in the build directory
[3] - https:/ /objectstorage. prodstack4- 5.canonical. com/v1/ AUTH_77e2ada1e7 a84929a74ba3b87 153c0ac/ autopkgtest- cosmic/ cosmic/ i386/d/ dahdi-linux/ 20180502_ 155702_ 8fd1e@/ log.gz
With that being said, I think it is safe to release debhelper for cosmic to make it a 'Valid Candidate'.