[Bug 2019465] Autopkgtest regression report (gcc-10/10.5.0-1ubuntu1~23.04)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gcc-10 (10.5.0-1ubuntu1~23.04) for lunar have finished running.
The following regressions have been reported in tests triggered by the package:

gcc-10/10.5.0-1ubuntu1~23.04 (amd64)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/lunar/update_excuses.html#gcc-10

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-10 in Ubuntu.
https://bugs.launchpad.net/bugs/2019465

Title:
  SRU: update gcc-10 to 10.5.0 and gcc-11 to 11.4.0

Status in gcc-10 package in Ubuntu:
  New
Status in gcc-10-cross package in Ubuntu:
  New
Status in gcc-10-cross-ports package in Ubuntu:
  New
Status in gcc-11 package in Ubuntu:
  New
Status in gcc-11-cross package in Ubuntu:
  New
Status in gcc-11-cross-mipsen package in Ubuntu:
  New
Status in gcc-11-cross-ports package in Ubuntu:
  New
Status in gcc-10 source package in Focal:
  Fix Committed
Status in gcc-10 source package in Jammy:
  Fix Committed
Status in gcc-10-cross source package in Jammy:
  Fix Committed
Status in gcc-10-cross-ports source package in Jammy:
  Fix Committed
Status in gcc-11 source package in Jammy:
  Fix Committed
Status in gcc-11-cross source package in Jammy:
  Fix Committed
Status in gcc-11-cross-ports source package in Jammy:
  Fix Committed
Status in gcc-10 source package in Kinetic:
  Fix Committed
Status in gcc-10-cross source package in Kinetic:
  Fix Committed
Status in gcc-10-cross-ports source package in Kinetic:
  Fix Committed
Status in gcc-11 source package in Kinetic:
  Fix Committed
Status in gcc-11-cross source package in Kinetic:
  Fix Committed
Status in gcc-11-cross-ports source package in Kinetic:
  Fix Committed
Status in gcc-10 source package in Lunar:
  Fix Committed
Status in gcc-10-cross source package in Lunar:
  Fix Committed
Status in gcc-10-cross-ports source package in Lunar:
  Fix Committed
Status in gcc-11 source package in Lunar:
  Fix Committed
Status in gcc-11-cross source package in Lunar:
  Fix Committed
Status in gcc-11-cross-mipsen source package in Lunar:
  Fix Committed
Status in gcc-11-cross-ports source package in Lunar:
  Fix Committed

Bug description:
  update gcc-11 to GCC 11.4.0
  update gcc-10 to GCC 10.5.0. Note that the GCC 10.5 release is expected in early July 2023. The test rebuilds mentioned below were done with a version taken from the gcc-10 branch.  GCC 10 is not used as a default compiler in all the targeted releases.

  There are no regressions in the gcc-10 and gcc-11 testsuites.

  Test rebuilds for main in lunar, kinetic and jammy were done. The
  analysis can be found in LP: #1995499.

  The packages were built in the ubuntu-toolchain-r/ppa PPA with only
  the security pocket enabled.

  The gcc-10 packages were done with the GCC 10.5.0 release candidate,
  and later updated to the final 10.5.0 release. The only change besides
  the version number is a bug fix in the D frontend.

  Test rebuilds for main in focal were done.
   
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230629-focal-focal.html
  https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230629-focal-gcc-focal.html

  There is one regression, dee on riscv64, timing out on the buildd in
  the testsuite. Newer uploads of the dee package have the testsuite
  disabled on riscv64, so apparently a known issue. We can backport that
  fix, if wanted.

  There are a few progressions: mir, python-openstacksdk, swift,
  udisks2, all riscv64 only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/2019465/+subscriptions