Closed
Bug 1874703
Opened 2 years ago
Closed 2 years ago
"'utf-8' codec can't decode byte 0xfc in position 74159: invalid start byte" when using push-to-lando
Categories
(Conduit :: Lando, defect)
Conduit
Lando
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1874438
People
(Reporter: ochameau, Unassigned)
References
(Blocks 1 open bug)
Details
See the two very last lines:
$ ./mach try fuzzy --query "'linux 'damp-webconsole" --rebuild 6 --message base --push-to-lando
Artifact builds enabled, pass --no-artifact to disable
estimates: Runs 4 tasks (2 selected, 2 dependencies)
estimates: Total task duration 0:45:25
estimates: In the top 97% of durations
estimates: Should take about 1:17:05 (Finished around 2024-01-15 06:42)
Access token is expired.
1. On your computer or mobile device navigate to: https://auth.mozilla.auth0.com/activate?user_code=xxxxx
2. Enter the following code: xxx
Waiting.....
Login successful.
Auth0 token validated.
Using 8b9cc7fb2c159d8625beef3e30b3015802305807 as the hg base commit.
Submitting stack of 628527 nodes and the try commit.
abort: error gathering patches for submission.
'utf-8' codec can't decode byte 0xfc in position 74159: invalid start byte
But may be something is broken on try as I don't see the jobs appearing on treeherder, even without --push-to-lando.
(Example of a manual push, without push-to-lando, it doesnt work: https://treeherder.mozilla.org/jobs?repo=try&revision=765aab87f3bfae40a042acc6212f1a879296f5e8)
Summary: "error gathering patches for submission" when using push-to-lando → "'utf-8' codec can't decode byte 0xfc in position 74159: invalid start byte" when using push-to-lando
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•