[Touch-packages] [Bug 1647635] Re: apport-retrace doesn't comment on bugs when add_gdb_info raises an IOError

2017-05-17 Thread Launchpad Bug Tracker 
This bug was fixed in the package apport - 2.20.5-0ubuntu3

---
apport (2.20.5-0ubuntu3) artful; urgency=medium

  * Revert change to test/test_crash_digger.py to use the source's
crash-digger.

 -- Brian Murray   Mon, 15 May 2017 16:00:06 -0700

** Changed in: apport (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1647635

Title:
  apport-retrace doesn't comment on bugs when add_gdb_info raises an
  IOError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  Looking at the retracer's activity on bug 1639215, we can see that the
  retracer did something because it removed the need-amd64-retrace tag
  but we don't know what.  It'd be helpful to know what happened during
  the retracing process rather than leaving people reading the bug in
  the dark.

  Looking at the retracing log files we see the following:

  ERROR: Invalid core dump: BFD: Warning: /tmp/apport_core_RVHov3 is
  truncated: expected core file size >= 2306977792, found: 2147479552.

  Looking at add_gdb_info we see the following:

  if 'is truncated: expected core file size' in out:
  ...
 raise IOError(reason)

  And apport-retrace does the following:

  try:
  report.add_gdb_info(sandbox)
  except IOError as e:
  apport.fatal(str(e))

  Instead of just exiting, apport-retrace should comment on the bug
  about the core dump being corrupt and call
  crashdb.mark_retrace_failed().

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1647635/+subscriptions

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

[Touch-packages] [Bug 1647635] Re: apport-retrace doesn't comment on bugs when add_gdb_info raises an IOError

2017-04-28 Thread Brian Murray 
** Tags removed: rls-z-incoming
** Tags added: rls-aa-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1647635

Title:
  apport-retrace doesn't comment on bugs when add_gdb_info raises an
  IOError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Looking at the retracer's activity on bug 1639215, we can see that the
  retracer did something because it removed the need-amd64-retrace tag
  but we don't know what.  It'd be helpful to know what happened during
  the retracing process rather than leaving people reading the bug in
  the dark.

  Looking at the retracing log files we see the following:

  ERROR: Invalid core dump: BFD: Warning: /tmp/apport_core_RVHov3 is
  truncated: expected core file size >= 2306977792, found: 2147479552.

  Looking at add_gdb_info we see the following:

  if 'is truncated: expected core file size' in out:
  ...
 raise IOError(reason)

  And apport-retrace does the following:

  try:
  report.add_gdb_info(sandbox)
  except IOError as e:
  apport.fatal(str(e))

  Instead of just exiting, apport-retrace should comment on the bug
  about the core dump being corrupt and call
  crashdb.mark_retrace_failed().

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1647635/+subscriptions

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

[Touch-packages] [Bug 1647635] Re: apport-retrace doesn't comment on bugs when add_gdb_info raises an IOError

2016-12-14 Thread Brian Murray 
Fixed in r3113.

** Changed in: apport
   Status: Triaged => Fix Released

** Changed in: apport (Ubuntu)
 Assignee: Brian Murray (brian-murray) => (unassigned)

** Changed in: apport (Ubuntu)
   Importance: Medium => Low

** Changed in: apport (Ubuntu)
Milestone: ubuntu-17.01 => None

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1647635

Title:
  apport-retrace doesn't comment on bugs when add_gdb_info raises an
  IOError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Looking at the retracer's activity on bug 1639215, we can see that the
  retracer did something because it removed the need-amd64-retrace tag
  but we don't know what.  It'd be helpful to know what happened during
  the retracing process rather than leaving people reading the bug in
  the dark.

  Looking at the retracing log files we see the following:

  ERROR: Invalid core dump: BFD: Warning: /tmp/apport_core_RVHov3 is
  truncated: expected core file size >= 2306977792, found: 2147479552.

  Looking at add_gdb_info we see the following:

  if 'is truncated: expected core file size' in out:
  ...
 raise IOError(reason)

  And apport-retrace does the following:

  try:
  report.add_gdb_info(sandbox)
  except IOError as e:
  apport.fatal(str(e))

  Instead of just exiting, apport-retrace should comment on the bug
  about the core dump being corrupt and call
  crashdb.mark_retrace_failed().

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1647635/+subscriptions

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

[Touch-packages] [Bug 1647635] Re: apport-retrace doesn't comment on bugs when add_gdb_info raises an IOError

2016-12-14 Thread Launchpad Bug Tracker 
** Branch linked: lp:apport

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1647635

Title:
  apport-retrace doesn't comment on bugs when add_gdb_info raises an
  IOError

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Looking at the retracer's activity on bug 1639215, we can see that the
  retracer did something because it removed the need-amd64-retrace tag
  but we don't know what.  It'd be helpful to know what happened during
  the retracing process rather than leaving people reading the bug in
  the dark.

  Looking at the retracing log files we see the following:

  ERROR: Invalid core dump: BFD: Warning: /tmp/apport_core_RVHov3 is
  truncated: expected core file size >= 2306977792, found: 2147479552.

  Looking at add_gdb_info we see the following:

  if 'is truncated: expected core file size' in out:
  ...
 raise IOError(reason)

  And apport-retrace does the following:

  try:
  report.add_gdb_info(sandbox)
  except IOError as e:
  apport.fatal(str(e))

  Instead of just exiting, apport-retrace should comment on the bug
  about the core dump being corrupt and call
  crashdb.mark_retrace_failed().

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1647635/+subscriptions

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

[Touch-packages] [Bug 1647635] Re: apport-retrace doesn't comment on bugs when add_gdb_info raises an IOError

2016-12-09 Thread Brian Murray 
** Changed in: apport (Ubuntu)
Milestone: None => ubuntu-17.01

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1647635

Title:
  apport-retrace doesn't comment on bugs when add_gdb_info raises an
  IOError

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Looking at the retracer's activity on bug 1639215, we can see that the
  retracer did something because it removed the need-amd64-retrace tag
  but we don't know what.  It'd be helpful to know what happened during
  the retracing process rather than leaving people reading the bug in
  the dark.

  Looking at the retracing log files we see the following:

  ERROR: Invalid core dump: BFD: Warning: /tmp/apport_core_RVHov3 is
  truncated: expected core file size >= 2306977792, found: 2147479552.

  Looking at add_gdb_info we see the following:

  if 'is truncated: expected core file size' in out:
  ...
 raise IOError(reason)

  And apport-retrace does the following:

  try:
  report.add_gdb_info(sandbox)
  except IOError as e:
  apport.fatal(str(e))

  Instead of just exiting, apport-retrace should comment on the bug
  about the core dump being corrupt and call
  crashdb.mark_retrace_failed().

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1647635/+subscriptions

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

[Touch-packages] [Bug 1647635] Re: apport-retrace doesn't comment on bugs when add_gdb_info raises an IOError

2016-12-06 Thread Brian Murray 
** Summary changed:

- apport-retrace doesn't comment on bugs when add_gdb_info raises and IOError
+ apport-retrace doesn't comment on bugs when add_gdb_info raises an IOError

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1647635

Title:
  apport-retrace doesn't comment on bugs when add_gdb_info raises an
  IOError

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Looking at the retracer's activity on bug 1639215, we can see that the
  retracer did something because it removed the need-amd64-retrace tag
  but we don't know what.  It'd be helpful to know what happened during
  the retracing process rather than leaving people reading the bug in
  the dark.

  Looking at the retracing log files we see the following:

  ERROR: Invalid core dump: BFD: Warning: /tmp/apport_core_RVHov3 is
  truncated: expected core file size >= 2306977792, found: 2147479552.

  Looking at add_gdb_info we see the following:

  if 'is truncated: expected core file size' in out:
  ...
 raise IOError(reason)

  And apport-retrace does the following:

  try:
  report.add_gdb_info(sandbox)
  except IOError as e:
  apport.fatal(str(e))

  Instead of just exiting, apport-retrace should comment on the bug
  about the core dump being corrupt and call
  crashdb.mark_retrace_failed().

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1647635/+subscriptions

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