Open Bug 1925459 Opened 24 days ago Updated 19 days ago

Many QuickSuggest.SuggestBackendRust Ingest error in test logs

Categories

(Firefox :: Address Bar, defect, P3)

defect

Tracking

()

ASSIGNED

People

(Reporter: florian, Assigned: adw)

Details

Test logs contain many errors like this:

[ERROR error_support::handling] suggest-unexpected: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base
console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error for Amo: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base"
[ERROR error_support::handling] suggest-unexpected: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base
console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error for Amp: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base"
[ERROR error_support::handling] suggest-unexpected: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base
console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error for Wikipedia: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base"
[ERROR error_support::handling] suggest-unexpected: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base
console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error for Mdn: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base"
[ERROR error_support::handling] suggest-unexpected: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base
console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error for Yelp: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base"

Example log file from a random bc job on mozilla-central: https://firefoxci.taskcluster-artifacts.net/YDeCBcnaSNu1YG08WHOvmQ/0/public/logs/live_backing.log

Drew, could you please evaluate this problem, and eventually set an appropriate priority and add to Jira?

Flags: needinfo?(adw)
Assignee: nobody → adw
Severity: -- → S4
Status: NEW → ASSIGNED
Flags: needinfo?(adw)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.