Public bug reported:

Hi,
while pushing an SRU I realized that on arm the kernels dep8 tests are somewhat 
shaky.
I think they work fine but in case there is more load on the boxes hosting the 
containers for the arm tests it times out (rather often).

Examples are [1], [2], [3] and it seems to occur in about 1/3 of the
cases when looking at [4].

I've seen the same on Yakkety and later. I saw it on Xenial as well, but
for whatever reason less often. Maybe it didn't have to compile so much
back then or the compiler does extra checks now?

However - we should consider if possible to add a testing hint that this takes 
a long++ time instead of letting it time out every now and then.
I'd not like to vote to disable the test, but as-is it is more a burden than a 
good quality indicator.

[1]: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/l/linux/20170519_222206_42d4b@/log.gz
[2]: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/l/linux/20170505_033350_3922b@/log.gz
[3]: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/l/linux/20170411_150605_f143c@/log.gz
[4]: http://autopkgtest.ubuntu.com/packages/linux/yakkety/armhf

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1694237

Title:
  autopkgtests crashing on arm64

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  while pushing an SRU I realized that on arm the kernels dep8 tests are 
somewhat shaky.
  I think they work fine but in case there is more load on the boxes hosting 
the containers for the arm tests it times out (rather often).

  Examples are [1], [2], [3] and it seems to occur in about 1/3 of the
  cases when looking at [4].

  I've seen the same on Yakkety and later. I saw it on Xenial as well,
  but for whatever reason less often. Maybe it didn't have to compile so
  much back then or the compiler does extra checks now?

  However - we should consider if possible to add a testing hint that this 
takes a long++ time instead of letting it time out every now and then.
  I'd not like to vote to disable the test, but as-is it is more a burden than 
a good quality indicator.

  [1]: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/l/linux/20170519_222206_42d4b@/log.gz
  [2]: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/l/linux/20170505_033350_3922b@/log.gz
  [3]: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/armhf/l/linux/20170411_150605_f143c@/log.gz
  [4]: http://autopkgtest.ubuntu.com/packages/linux/yakkety/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694237/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to