1209691 - Autophone - handle incorrect logcat dates emitted by devices.

Status: RESOLVED FIXED

(Testing Graveyard :: Autophone, defect)

Description

[Bob Clary [:bc] (inactive)]

I found that one of my local devices sometimes (usually after a Unit Test) will emit logcat messages with fixed-bogus dates.

11-30 19:49:24.551 I/Vold    (  211): Vold 2.1 (the revenge) firing up
11-30 19:49:24.561 E/Vold    (  211): created DirEncryptionManager
11-30 19:49:24.571 D/Vold    (  211): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
11-30 19:49:24.571 D/Vold    (  211): Volume sda state changing -1 (Initializing) -> 0 (No-Media)
11-30 19:49:24.571 D/Vold    (  211): Volume sdb state changing -1 (Initializing) -> 0 (No-Media)
11-30 19:49:24.571 D/Vold    (  211): Volume sdc state changing -1 (Initializing) -> 0 (No-Media)
11-30 19:49:24.571 D/Vold    (  211): Volume sdd state changing -1 (Initializing) -> 0 (No-Media)
11-30 19:49:24.571 D/Vold    (  211): Volume sde state changing -1 (Initializing) -> 0 (No-Media)
11-30 19:49:24.571 D/Vold    (  211): Volume sdf state changing -1 (Initializing) -> 0 (No-Media)
11-30 19:49:24.591 D/DirectVolume(  211): DirectVolume::readId -> path '/sys/devices/platform/msm_sdcc.3/mmc_host/mmc1/mmc1:0007/block/mmcblk1/device/cid' 
11-30 19:49:24.591 D/DirectVolume(  211): DirectVolume::readId -> id '275048534438474230700d45b000b90c' 
11-30 19:49:24.591 D/DirectVolume(  211): DirectVolume::handleDiskAdded -> mDiskMajor 179, mDiskMinor 96, NPARTS:1
11-30 19:49:24.591 D/Vold    (  211): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
11-30 19:49:24.591 D/DirectVolume(  211): DirectVolume::handlePartitionAdded -> major 179, minor 97, PARTN 1
11-30 19:49:24.591 D/Vold    (  211): Volume sdcard state changing 2 (Pending) -> 1 (Idle-Unmounted)
09-29 02:42:21.685 I/PackageParser(  534): XXX.XXXXXXXX.XXXXXXX.XXXX.XXXXXXXX: compat added XXXXXXX.XXXXXXXXXX.XXXXXXXXXXXXXXXXXXXXXX XXXXXXX.XXXXXXXXXX.XXXXXXXXXX
09-29 02:42:21.755 W/PackageParser(  534): No actions in intent filter at /system/app/SmartcardService.apk Binary XML file line #51
09-29 02:42:21.755 W/PackageParser(  534): No actions in intent filter at /system/app/SMemo.apk Binary XML file line #125
09-29 02:42:21.755 W/PackageParser(  534): No actions in intent filter at /system/app/SMemo.apk Binary XML file line #141
09-29 02:42:21.755 W/PackageParser(  534): No actions in intent filter at /system/app/SMemo.apk Binary XML file line #172
09-29 02:42:21.755 W/PackageParser(  534): No actions in intent filter at /system/app/SMemo.apk Binary XML file line #184
09-29 02:42:21.755 W/PackageParser(  534): No actions in intent filter at /system/app/SMemo.apk Binary XML file line #192

I don't know if this is a general occurrence or if it only happens on my Samsung Galaxy S3, but it is a potential cause of errors both in collecting the logcat messages and in analyzing them for s1s2 and webappstartup tests.

Comment 1

[Bob Clary [:bc] (inactive)]

Attachment: bug-1209691-handle-incorrect-logcat-dates-v1.patch

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

Comment on attachment 8667538 [details] [diff] [review]
bug-1209691-handle-incorrect-logcat-dates-v1.patch

Review of attachment 8667538 [details] [diff] [review]:
-----------------------------------------------------------------

the code has lots of comments, I get the sense we could make this cleaner- but after looking at it 3 times I couldn't come up with a simpler solution.

Comment 3

[Bob Clary [:bc] (inactive)]

https://github.com/mozilla/autophone/commit/27e01f8bdc1c7f6b79c7ba7d43811555cd30df61