[SRU] Upgrade to 15.0.7 on Kinetic and Jammy

Bug #2008755 reported by Zixing Liu
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
llvm-toolchain-15 (Ubuntu)
Fix Released
Undecided
Unassigned
Jammy
Fix Released
Undecided
Timo Aaltonen
Kinetic
Fix Released
Undecided
Unassigned

Bug Description

[ Impact ]

 * LLVM 15 version 15.0.7 fixed an issue where in certain cases, the LLVM register allocator would trigger an assertion error (or an abort() in the release build) on ppc64el during the RTL phase.

[ Test Plan ]

 * Building Rust 1.65 or above can reproduce this issue. See https://launchpad.net/~liushuyu-011/+archive/ubuntu/rust-updates-1.66/+build/25610577.
 * Or run `llc -O0` on this sample: https://github.com/llvm/llvm-project/files/10078103/reduced.ll.txt.

[ Where problems could occur ]

 * The problems may occur through LLVM optimizer crashes or IR lowering issues.

 * The risk of other severe issues occurring in the 15.0.7 is relatively low since LLVM upstream should have done their testing before release.

 * LLVM 15 is currently only used by the HWE stack in JJ and KK, so a rebuild test for the HWE stack should suffice, in addition to the tests included by Rust.

[ Other Info ]

 * Upstream bug report: https://github.com/llvm/llvm-project/issues/59172

description: updated
Revision history for this message
Timo Aaltonen (tjaalton) wrote :
Changed in llvm-toolchain-15 (Ubuntu):
status: New → Fix Released
Changed in llvm-toolchain-15 (Ubuntu Jammy):
assignee: nobody → Timo Aaltonen (tjaalton)
status: New → In Progress
Changed in llvm-toolchain-15 (Ubuntu Kinetic):
status: New → In Progress
Revision history for this message
Zixing Liu (liushuyu-011) wrote :

> fyi, test builds running at https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

Thank you! My tests indicate your new builds can fix the issue described in this LP bug report.

Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Zixing, or anyone else affected,

Accepted llvm-toolchain-15 into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm-toolchain-15/1:15.0.7-0ubuntu0.22.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in llvm-toolchain-15 (Ubuntu Kinetic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-kinetic
Changed in llvm-toolchain-15 (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed-jammy
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Zixing, or anyone else affected,

Accepted llvm-toolchain-15 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/llvm-toolchain-15/1:15.0.7-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Zixing Liu (liushuyu-011) wrote :

Hi there,

I can confirm the issue has been fixed. Please see attached logs for verification method and results (the input file used can be found in the bug description).

Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (llvm-toolchain-15/1:15.0.7-0ubuntu0.22.10.1)

All autopkgtests for the newly accepted llvm-toolchain-15 (1:15.0.7-0ubuntu0.22.10.1) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

dkms/3.0.6-2ubuntu2 (i386)
ycmd/0+20220401+gitdbe806f+ds-3ubuntu1 (amd64, armhf)

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/kinetic/update_excuses.html#llvm-toolchain-15

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

Thank you!

Revision history for this message
Zixing Liu (liushuyu-011) wrote :

> The following regressions have been reported in tests triggered by the package:

> dkms/3.0.6-2ubuntu2 (i386)

This needs to run a migration-reference/0 to determine whether this is genuinely a regression caused by this SRU.

> ycmd/0+20220401+gitdbe806f+ds-3ubuntu1 (amd64, armhf)

This needs a retry.

Revision history for this message
Zixing Liu (liushuyu-011) wrote :

All the tests are now passing and awaiting the migration.

tags: added: verification-done verification-done-jammy verification-done-kinetic
removed: verification-needed verification-needed-jammy verification-needed-kinetic
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package llvm-toolchain-15 - 1:15.0.7-0ubuntu0.22.04.1

---------------
llvm-toolchain-15 (1:15.0.7-0ubuntu0.22.04.1) jammy; urgency=medium

  * New upstream stable release. (LP: #2008755)

 -- Timo Aaltonen <email address hidden> Wed, 01 Mar 2023 15:58:23 +0200

Changed in llvm-toolchain-15 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Steve Langasek (vorlon) wrote : Update Released

The verification of the Stable Release Update for llvm-toolchain-15 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package llvm-toolchain-15 - 1:15.0.7-0ubuntu0.22.10.1

---------------
llvm-toolchain-15 (1:15.0.7-0ubuntu0.22.10.1) kinetic; urgency=medium

  * New upstream stable release. (LP: #2008755)

 -- Timo Aaltonen <email address hidden> Wed, 01 Mar 2023 15:58:23 +0200

Changed in llvm-toolchain-15 (Ubuntu Kinetic):
status: Fix Committed → Fix Released
Revision history for this message
Sylvestre Ledru (sylvestre) wrote :

why you didn't sync the package from Debian directly?
it has a bunch of fixes:
https://tracker.debian.org/pkg/llvm-toolchain-15
In general, if I may, you should take llvm-toolchain from Debian and not patch it directly in Ubuntu

And this patch broke packages coming from apt.llvm.org

(Reading database ... 246672 files and directories currently installed.)
274
Preparing to unpack .../libpolly-15-dev_1%3a15.0.7~++20230315075603+8dfdcc7b7bf6-1~exp1~20230315195652.107_amd64.deb ...
275
Unpacking libpolly-15-dev:amd64 (1:15.0.7~++20230315075603+8dfdcc7b7bf6-1~exp1~20230315195652.107) ...
276
dpkg: error processing archive /var/cache/apt/archives/libpolly-15-dev_1%3a15.0.7~++20230315075603+8dfdcc7b7bf6-1~exp1~20230315195652.107_amd64.deb (--unpack):
277
 trying to overwrite '/usr/lib/llvm-15/include/polly/Canonicalization.h', which is also in package libclang-common-15-dev 1:15.0.7-0ubuntu0.22.04.1

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

packaging changes like splitting libclang-common-dev is not SRU material, the goal for this SRU was to update to latest upstream version, that's all

Revision history for this message
Gerald Combs (gerald.combs) wrote :

This has broken our ability to install libclang-rt-15-dev from apt.llvm.org:

Preparing to unpack .../06-libclang-common-15-dev_1%3a15.0.7-0ubuntu0.22.04.1_amd64.deb ...
Unpacking libclang-common-15-dev (1:15.0.7-0ubuntu0.22.04.1) over (1:15.0.7~++20230131104537+8dfdcc7b7bf6-1~exp1~20230131104626.110) ...
dpkg: error processing archive /tmp/apt-dpkg-install-i84rnS/06-libclang-common-15-dev_1%3a15.0.7-0ubuntu0.22.04.1_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/llvm-15/lib/clang/15.0.7/README.txt', which is also in package libclang-rt-15-dev:amd64 1:15.0.7~++20230131104537+8dfdcc7b7bf6-1~exp1~20230131104626.110
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

We're working around the issue with `apt-get --option DPkg::options::="--force-overwrite" install llvm-15` but are looking for a more proper fix.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

well it's too bad that external repositories use packaging that split things during a stable series, so don't expect a fix from the distro

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.