[Bug 1962454] Re: Oops pages show wrong time window in JournalErrors
Daniel van Vugt
1962454 at bugs.launchpad.net
Mon Jul 11 06:58:30 UTC 2022
** Description changed:
[Impact]
Oops pages show wrong time window in JournalErrors. For example, I just
experienced a crash at:
Feb 28 17:31:12
And the JournalErrors entries are:
Feb 28 17:31:30 - Feb 28 17:31:41
So don't relate to the crash.
[Test Plan]
1. Find a recent crash report from a relevant Ubuntu release on
https://errors.ubuntu.com/ If you're looking at
https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a
relevant instance from the Occurrences list.
2. Now you're on a page starting with https://errors.ubuntu.com/oops/
look at Dependencies and verify that apport is a recent enough version
to contain the proposed fix.
- 3. Expand the JournalErrors field and verify the Date field above it
- falls within the time range of the JournalErrors entries.
+ 3. Verify the Date field falls within the time range of the
+ JournalErrors entries.
+
+ 4. Step 3 might have failed in the case of there being no system log
+ entries at all written to disk around the time of the crash. That does
+ not necessarily mean the test plan has failed. Goto step 1 and pick a
+ different crash.
[Where problems could occur]
Worst case - in any part of the bug reporting/collection procedure,
since that is what's changing.
[Other Info]
** Description changed:
[Impact]
Oops pages show wrong time window in JournalErrors. For example, I just
experienced a crash at:
Feb 28 17:31:12
And the JournalErrors entries are:
Feb 28 17:31:30 - Feb 28 17:31:41
So don't relate to the crash.
[Test Plan]
1. Find a recent crash report from a relevant Ubuntu release on
https://errors.ubuntu.com/ If you're looking at
https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a
relevant instance from the Occurrences list.
2. Now you're on a page starting with https://errors.ubuntu.com/oops/
- look at Dependencies and verify that apport is a recent enough version
+ look at ApportVersion and verify that apport is a recent enough version
to contain the proposed fix.
3. Verify the Date field falls within the time range of the
JournalErrors entries.
4. Step 3 might have failed in the case of there being no system log
entries at all written to disk around the time of the crash. That does
not necessarily mean the test plan has failed. Goto step 1 and pick a
different crash.
[Where problems could occur]
Worst case - in any part of the bug reporting/collection procedure,
since that is what's changing.
[Other Info]
** Description changed:
[Impact]
Oops pages show wrong time window in JournalErrors. For example, I just
experienced a crash at:
Feb 28 17:31:12
And the JournalErrors entries are:
Feb 28 17:31:30 - Feb 28 17:31:41
So don't relate to the crash.
[Test Plan]
1. Find a recent crash report from a relevant Ubuntu release on
https://errors.ubuntu.com/ If you're looking at
https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a
relevant instance from the Occurrences list.
2. Now you're on a page starting with https://errors.ubuntu.com/oops/
look at ApportVersion and verify that apport is a recent enough version
to contain the proposed fix.
3. Verify the Date field falls within the time range of the
JournalErrors entries.
- 4. Step 3 might have failed in the case of there being no system log
+ Step 3 might have failed in the case of there being no system log
entries at all written to disk around the time of the crash. That does
not necessarily mean the test plan has failed. Goto step 1 and pick a
different crash.
+
+ Prior to the fix you would almost never find oops pages that would pass
+ the test. After the fix you should find many/most oops pages do pass the
+ test.
[Where problems could occur]
Worst case - in any part of the bug reporting/collection procedure,
since that is what's changing.
[Other Info]
** Description changed:
[Impact]
Oops pages show wrong time window in JournalErrors. For example, I just
experienced a crash at:
Feb 28 17:31:12
And the JournalErrors entries are:
Feb 28 17:31:30 - Feb 28 17:31:41
So don't relate to the crash.
[Test Plan]
1. Find a recent crash report from a relevant Ubuntu release on
https://errors.ubuntu.com/ If you're looking at
https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a
relevant instance from the Occurrences list.
2. Now you're on a page starting with https://errors.ubuntu.com/oops/
look at ApportVersion and verify that apport is a recent enough version
- to contain the proposed fix.
+ to contain the proposed fix. If not then go to step 1.
3. Verify the Date field falls within the time range of the
- JournalErrors entries.
-
- Step 3 might have failed in the case of there being no system log
- entries at all written to disk around the time of the crash. That does
- not necessarily mean the test plan has failed. Goto step 1 and pick a
- different crash.
+ JournalErrors entries. This *may* fail in the case of there being no
+ system log entries at all written to disk around the time of the crash.
+ That does not necessarily mean the test plan has failed. Go to step 1
+ and pick a different crash.
Prior to the fix you would almost never find oops pages that would pass
the test. After the fix you should find many/most oops pages do pass the
test.
[Where problems could occur]
Worst case - in any part of the bug reporting/collection procedure,
since that is what's changing.
[Other Info]
** Description changed:
[Impact]
Oops pages show wrong time window in JournalErrors. For example, I just
experienced a crash at:
Feb 28 17:31:12
And the JournalErrors entries are:
Feb 28 17:31:30 - Feb 28 17:31:41
So don't relate to the crash.
[Test Plan]
1. Find a recent crash report from a relevant Ubuntu release on
https://errors.ubuntu.com/ If you're looking at
https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick a
relevant instance from the Occurrences list.
2. Now you're on a page starting with https://errors.ubuntu.com/oops/
look at ApportVersion and verify that apport is a recent enough version
to contain the proposed fix. If not then go to step 1.
3. Verify the Date field falls within the time range of the
- JournalErrors entries. This *may* fail in the case of there being no
- system log entries at all written to disk around the time of the crash.
- That does not necessarily mean the test plan has failed. Go to step 1
- and pick a different crash.
+ JournalErrors entries.
+
+ Step 3 might fail in the case of there being no system log entries from
+ around the time of the crash. That does not necessarily mean the test
+ plan has failed. Go to step 1 and pick a different crash.
Prior to the fix you would almost never find oops pages that would pass
the test. After the fix you should find many/most oops pages do pass the
test.
[Where problems could occur]
Worst case - in any part of the bug reporting/collection procedure,
since that is what's changing.
[Other Info]
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1962454
Title:
Oops pages show wrong time window in JournalErrors
Status in Apport:
Fix Released
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Jammy:
Incomplete
Bug description:
[Impact]
Oops pages show wrong time window in JournalErrors. For example, I
just experienced a crash at:
Feb 28 17:31:12
And the JournalErrors entries are:
Feb 28 17:31:30 - Feb 28 17:31:41
So don't relate to the crash.
[Test Plan]
1. Find a recent crash report from a relevant Ubuntu release on
https://errors.ubuntu.com/ If you're looking at
https://errors.ubuntu.com/problem/SOMETHING then scroll down and pick
a relevant instance from the Occurrences list.
2. Now you're on a page starting with https://errors.ubuntu.com/oops/
look at ApportVersion and verify that apport is a recent enough
version to contain the proposed fix. If not then go to step 1.
3. Verify the Date field falls within the time range of the
JournalErrors entries.
Step 3 might fail in the case of there being no system log entries
from around the time of the crash. That does not necessarily mean the
test plan has failed. Go to step 1 and pick a different crash.
Prior to the fix you would almost never find oops pages that would
pass the test. After the fix you should find many/most oops pages do
pass the test.
[Where problems could occur]
Worst case - in any part of the bug reporting/collection procedure,
since that is what's changing.
[Other Info]
To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1962454/+subscriptions
More information about the foundations-bugs
mailing list