[SRU] lcov 2.0-1 FTBFS on Mantic

Bug #2051166 reported by Sudip Mukherjee
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lcov (Ubuntu)
Fix Released
Undecided
Unassigned
Mantic
Fix Released
Undecided
Unassigned

Bug Description

[ Impact ]

lcov fails to build on Mantic with the error:

   dh_auto_test
        make -j8 test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make[2]: Entering directory '/<<PKGBUILDDIR>>/tests'
/<<PKGBUILDDIR>>/tests//bin/mkinfo: Could not create directory src/: File exists
/<<PKGBUILDDIR>>/tests//bin/mkinfo: Could not create directory src/: File exists
Creating coverage files (2 tests, 5 source files)
  Source tree ......... Creating coverage files (2 tests, 5 source files)
  Source tree ......... make[2]: *** [common.mak:75: /<<PKGBUILDDIR>>/tests/target.info] Error 17
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [common.mak:75: /<<PKGBUILDDIR>>/tests/full.info] Error 17
Could not create directory /<<PKGBUILDDIR>>/tests/src/build/info
done (950 lines, 50 functions, 3428 branches)
  Full coverage ....... make[2]: *** [common.mak:75: /<<PKGBUILDDIR>>/tests/zero.counts] Error 2

[ Test Plan ]

 * lcov should build on Mantic

- A basic testplan to check it works after build:
 * install lcov
 * execute "lcov --help"

[ Where problems could occur ]

 * There is no change in the code, it only disables Multi threading while building. So, user should not see any change in the known behaviour.

[ Other Info ]

 * Debian has disabled the tests becaue of the failure. But imho, its better to have the tests running on build.
 * I have also sent the chane to Debian - https://salsa.debian.org/mckinstry/lcov/-/merge_requests/2

[ Original Bug Description ]

Fails to build in Mantic with the error:

   dh_auto_test
        make -j8 test
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make[2]: Entering directory '/<<PKGBUILDDIR>>/tests'
/<<PKGBUILDDIR>>/tests//bin/mkinfo: Could not create directory src/: File exists
/<<PKGBUILDDIR>>/tests//bin/mkinfo: Could not create directory src/: File exists
Creating coverage files (2 tests, 5 source files)
  Source tree ......... Creating coverage files (2 tests, 5 source files)
  Source tree ......... make[2]: *** [common.mak:75: /<<PKGBUILDDIR>>/tests/target.info] Error 17
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [common.mak:75: /<<PKGBUILDDIR>>/tests/full.info] Error 17
Could not create directory /<<PKGBUILDDIR>>/tests/src/build/info
done (950 lines, 50 functions, 3428 branches)
  Full coverage ....... make[2]: *** [common.mak:75: /<<PKGBUILDDIR>>/tests/zero.counts] Error 2

Debian has disabled the tests as they hang.

https://salsa.debian.org/mckinstry/lcov/-/commit/b62a70d32688e3de8898177eeb1928f1344fa567

Revision history for this message
Sudip Mukherjee (sudipmuk) wrote :

The options are either to disable the tests completely or disable multi-threading and keep the tests enabled.

Debian MR at https://salsa.debian.org/mckinstry/lcov/-/merge_requests/2

Revision history for this message
Sudip Mukherjee (sudipmuk) wrote :

This is being done via #2029924

Changed in lcov (Ubuntu Mantic):
status: New → Confirmed
Changed in lcov (Ubuntu):
status: New → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

missing sru information

Revision history for this message
Sudip Mukherjee (sudipmuk) wrote :

Sorry for missing it, I assumed the SRU information at #2029924 will cover this also. But has now been added.

description: updated
summary: - lcov 2.0-1 FTBFS on Mantic
+ [SRU] lcov 2.0-1 FTBFS on Mantic
Changed in lcov (Ubuntu Mantic):
status: Confirmed → In Progress
Revision history for this message
Robie Basak (racb) wrote :

Thank you for working on this!

I agree that keeping the tests but disabling parallel builds is a better way forwards.

But if it is the selected way forward for Ubuntu, then this should be done in Noble also by introducing a delta, rather than Noble being behind in this compared to Mantic because it is using Debian's current fix of disabling the tests instead.

So I'll accept this into mantic-proposed, but before it is released to mantic-updates, please could you upload the same fix to Noble?

Changed in lcov (Ubuntu Mantic):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-mantic
Revision history for this message
Robie Basak (racb) wrote : Please test proposed package

Hello Sudip, or anyone else affected,

Accepted lcov into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lcov/2.0-1ubuntu0.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-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. 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
Robie Basak (racb) wrote :

> So I'll accept this into mantic-proposed, but before it is released to mantic-updates, please could you upload the same fix to Noble?

I just sponsored an upload to Noble to address this - see bug 2052836.

Revision history for this message
Sudip Mukherjee (sudipmuk) wrote :

I gues I can mark it as verification-done as the FTBFS is fixed and the package is in mantic-proposed. But #2029924 is verification-failed and is waiting for an incremental fix sponsor.

tags: added: verification-done verification-done-mantic
removed: verification-needed verification-needed-mantic
Revision history for this message
Andreas Hasenack (ahasenack) wrote :

The changes file that was accepted didn't include version 0.1, which is the one that fixed this bug here. Marking it "fix released" manually, since I just released https://bugs.launchpad.net/ubuntu/+source/lcov/+bug/2029924

Changed in lcov (Ubuntu Mantic):
status: Fix Committed → Fix Released
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.