This change in apport modified the way that crash signatures are calculated for python crashes and subsequently we have some buckets that have use the old crash signature. For example:
It may be a good idea to look for oopses with a crash signature that has the string '<module>' in them and recreate the crash_signature and then rebucket those oopses.
This change in apport modified the way that crash signatures are calculated for python crashes and subsequently we have some buckets that have use the old crash signature. For example:
https:/ /errors. ubuntu. com/bucket/ ?id=/usr/ share/unattende d-upgrades/ unattended- upgrade- shutdown% 3AValueError% 3A%3Cmodule% 3E
I download an instance in this bucket:
PYTHONPATH= /home/bdmurray/ source- trees/daisy/ daisy tools/create_ apport_ report. py 658f7a70- 4957-11e2- 872a-e4115b0f8a 4a unattended.crash
and resubmitted the crash and it appeared in a different bucket:
https:/ /errors. ubuntu. com/bucket/ ?id=/usr/ share/unattende d-upgrades/ unattended- upgrade- shutdown: ValueError: /usr/share/ unattended- upgrades/ unattended- upgrade- shutdown@ 34
This bucket is more specific than the previous one. This could also be confirmed via the following:
import apport load(open( '/home/ bdmurray/ unattended. crash', 'rb')) crash_signature () share/unattende d-upgrades/ unattended- upgrade- shutdown: ValueError: /usr/share/ unattended- upgrades/ unattended- upgrade- shutdown@ 34'
report = apport.Report()
crash_sig = report.
report.
u'/usr/
It may be a good idea to look for oopses with a crash signature that has the string '<module>' in them and recreate the crash_signature and then rebucket those oopses.