Use Log.e for procfs file read errors
Log.wtf implies a catastrophic, unrecoverable failure. Failures to read procfs files (e.g., due to permissions or non-existence) are better represented by Log.e as they are often recoverable or expected under certain conditions, and not always indicative of a fatal application state. Flag: EXEMPT mainline Bug: 429012888 Test: TH Change-Id: I717d46d4c3802ac478e80d2a9dd28c79a9ebc5f7
This commit is contained in:
parent
27013988a7
commit
83298a7b5d
1 changed files with 1 additions and 1 deletions
|
|
@ -78,7 +78,7 @@ public final class ProcfsParsingUtils {
|
|||
lines.add(line);
|
||||
}
|
||||
} catch (IOException e) {
|
||||
Log.wtf(TAG, "failed to read " + filePath, e);
|
||||
Log.e(TAG, "failed to read " + filePath, e);
|
||||
}
|
||||
|
||||
return lines;
|
||||
|
|
|
|||
Loading…
Reference in a new issue