adt tests fail on zesty for apport

They are also failing on yakkety.

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/a/apport/20170116_093836_30f5e@/log.gz

It seems we have the same issue on yakkety right now: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/a/apport/20170116_093629_30f5e@/log.gz

Is there any update on this?

The tests for artful are now failing for a different reason:

======================================================================
ERROR: test_add_gdb_info_abort_glib (__main__.T)
add_gdb_info() with glib assertion
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test_report.py", line 852, in test_add_gdb_info_abort_glib
    self.assertTrue(pr['AssertionMessage'].startswith('ERROR:<stdin>:2:main: assertion failed (1 < 0):'),
  File "/usr/lib/python3.5/collections/__init__.py", line 989, in __getitem__
    raise KeyError(key)
KeyError: 'AssertionMessage'

I've spent some time digging into this and it seems "print __glib_assert_msg" is behaving differently and has been for a bit.

I did notice that, but did not dig into that failure, as I wanted to only
fix the gpg stuff.

On 6 May 2017 at 00:16, Brian Murray <email address hidden> wrote:

> The tests for artful are now failing for a different reason:
>
> ======================================================================
> ERROR: test_add_gdb_info_abort_glib (__main__.T)
> add_gdb_info() with glib assertion
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "./test_report.py", line 852, in test_add_gdb_info_abort_glib
> self.assertTrue(pr['AssertionMessage'].startswith('ERROR:<stdin>:2:main:
> assertion failed (1 < 0):'),
> File "/usr/lib/python3.5/collections/__init__.py", line 989, in
> __getitem__
> raise KeyError(key)
> KeyError: 'AssertionMessage'
>
> I've spent some time digging into this and it seems "print
> __glib_assert_msg" is behaving differently and has been for a bit.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1651623
>
> Title:
> adt tests fail on zesty for apport
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/
> 1651623/+subscriptions
>

--
Regards,

Dimitri.

Sure, I was mostly making a note for myself since it was Friday. ;-)

On Sat, May 06, 2017 at 06:39:32PM -0000, Dimitri John Ledkov wrote:
> I did notice that, but did not dig into that failure, as I wanted to only
> fix the gpg stuff.
>
> On 6 May 2017 at 00:16, Brian Murray <email address hidden> wrote:
>
> > The tests for artful are now failing for a different reason:
> >
> > ======================================================================
> > ERROR: test_add_gdb_info_abort_glib (__main__.T)
> > add_gdb_info() with glib assertion
> > ----------------------------------------------------------------------
> > Traceback (most recent call last):
> > File "./test_report.py", line 852, in test_add_gdb_info_abort_glib
> > self.assertTrue(pr['AssertionMessage'].startswith('ERROR:<stdin>:2:main:
> > assertion failed (1 < 0):'),
> > File "/usr/lib/python3.5/collections/__init__.py", line 989, in
> > __getitem__
> > raise KeyError(key)
> > KeyError: 'AssertionMessage'
> >
> > I've spent some time digging into this and it seems "print
> > __glib_assert_msg" is behaving differently and has been for a bit.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1651623
> >
> > Title:
> > adt tests fail on zesty for apport
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/
> > 1651623/+subscriptions
> >
>
>
> --
> Regards,
>
> Dimitri.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1651623
>
> Title:
> adt tests fail on zesty for apport
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+subscriptions
>
--
Brian Murray

This bug was fixed in the package apport - 2.20.4-0ubuntu6

---------------
apport (2.20.4-0ubuntu6) artful; urgency=medium

   * Disable report.test_add_gdb_info_abort_glib test case for now, as the
     glib assertion message is broken under current Ubuntu (LP: #1689344)
  * etc/apport/crashdb.conf: Enable Launchpad crash reports for artful.

 -- Brian Murray <email address hidden> Mon, 08 May 2017 11:10:34 -0700

Hello Dimitri, or anyone else affected,

Accepted apport into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.4-0ubuntu4.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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

Hello Dimitri, or anyone else affected,

Accepted apport into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apport/2.20.3-0ubuntu8.3 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, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

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

Some autopkgtests fail on xenial but not for this reason, so I'm setting the task to Invalid.

Setting to v-done for yakkety:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/amd64/a/apport/20170512_193229_92825@/log.gz

Setting to v-done for zesty:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20170512_193953_7d1ed@/log.gz

This bug was fixed in the package apport - 2.20.4-0ubuntu4.1

---------------
apport (2.20.4-0ubuntu4.1) zesty; urgency=medium

  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
    glib assertion message is broken under current Ubuntu (LP: #1689344)
  * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
    with apt key ring. Thanks to Dimitri John Ledkov for the patch.
    (LP: #1651623)

 -- Brian Murray <email address hidden> Wed, 10 May 2017 17:05:11 -0700

The verification of the Stable Release Update for apport has completed successfully and the package has now been 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.

This bug was fixed in the package apport - 2.20.3-0ubuntu8.3

---------------
apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium

  * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues
    with apt key ring. Thanks to Dimitri John Ledkov for the patch.
    (LP: #1651623)
  * Disable report.test_add_gdb_info_abort_glib test case for now, as the
    glib assertion message is broken under current Ubuntu (LP: #1689344)
  * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in
    every report. (LP: #1673557)

 -- Brian Murray <email address hidden> Wed, 10 May 2017 18:10:32 -0700