action #138590
closedtest year_2038_detection: too much detail on data source (implementation detail)
100%
Description
Observation¶
The y2j38test goes directly onto utmp/wtmp to identify if the system is y2k38 compatible. This is wrong insofar that those files will never be y2k38 compatible
Instead of testing utmp/wtmp directly, the code should test consumers of the data sources, such as
- last
- w
- who
To fix the y2k38 issue, the data is moved to a new database (without breaking ABI of existing consumers); in recent installations, var/log/wtmp for example does not exist at all anymore, only the new location
openQA test in scenario microos-Staging:J-Staging-DVD-x86_64-microos@uefi-staging fails in
year_2038_detection
Test suite description¶
Reproducible¶
Fails since (at least) Build J.563.1
Expected result¶
Last good: J.562.1 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by dimstar about 1 year ago
- Subject changed from test year_2038_detection: too much detail on data source to test year_2038_detection: too much detail on data source (implementation detail)
Updated by kukuk about 1 year ago
/run/utmp will also go away with the next systemd submission.
So don't reference /run/utmp and /var/log/wtmp anymore in any test.
Updated by favogt about 1 year ago
- Assignee set to favogt
I'll take this. FWICT who, w and last -F are the most relevant commands. Anything else?
Updated by favogt about 1 year ago
- Status changed from New to Resolved
- % Done changed from 0 to 100