Closed Bug 1636957 Opened 6 years ago Closed 5 years ago

ERROR ffi_support::ffistr] Invalid UTF-8 was passed to rust! Utf8Error { valid_up_to: 2, error_len: Some(1) }

Categories

(Data Platform and Tools :: Glean: SDK, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: Dexter, Unassigned)

Details

I started seeing this today in my Android test logs:

[Robolectric] mozilla.telemetry.glean.private.LabeledMetricTypeTest.test labeled counter type: sdk=28; resources=BINARY
I/MonitoringInstr: Instrumentation started!
I/MonitoringInstr: Setting context classloader to 'org.robolectric.internal.AndroidSandbox$SdkSandboxClassLoader@dd3b207', Original: 'org.robolectric.internal.AndroidSandbox$SdkSandboxClassLoader@dd3b207'
I/glean/Glean: Registering pings for mozilla.telemetry.glean.GleanMetrics.Pings
E/glean/MetricsPingSched: MetricsPingScheduler last stored ping time was not valid
I/glean/MetricsPingSched: The 'metrics' ping is scheduled for immediate collection, Mon May 11 16:14:50 CEST 2020
I/glean/MetricsPingSched: Collecting the 'metrics' ping, now = Mon May 11 16:14:50 CEST 2020, startup = true, reason = overdue
D/glean/MetricsPingSched: Scheduling the 'metrics' ping in 42309094ms
[2020-05-11T14:14:50Z ERROR ffi_support::ffistr] Invalid UTF-8 was passed to rust! Utf8Error { valid_up_to: 2, error_len: Some(1) }

Priority: -- → P3
Whiteboard: [telemetry:glean-rs:m?]

Did it actually crash any test?

(In reply to Jan-Erik Rediger [:janerik] from comment #1)

Did it actually crash any test?

Nope, it didn't.

Priority: P3 → P2
Whiteboard: [telemetry:glean-rs:m?]

We never followed up on this, but I also never saw it in my own tests or on CI.

:Dexter, can we close this as incomplete?

Flags: needinfo?(alessio.placitelli)

Yes!

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(alessio.placitelli)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.