l10n-central Japanese repository does not find revision: error "filtered revision 'e6c3fe91a9702d15ff37ce5b447d5a41629965b1' (not in 'replicatedserved' subset)"
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Tracking
(Not tracked)
People
(Reporter: aryx, Unassigned)
Details
Code sheriffs run a central-as-beta simulation every day. Today it hit an issue creating a Japanese build, one of the 5 locales included.
From the log:
[task 2024-03-09T14:22:37.401Z] 14:22:37 ERROR - Traceback (most recent call last):
[task 2024-03-09T14:22:37.401Z] 14:22:37 INFO - File "/builds/worker/checkouts/gecko/python/mozbuild/mozbuild/action/langpack_manifest.py", line 81, in get_pushlog
[task 2024-03-09T14:22:37.401Z] 14:22:37 INFO - response.raise_for_status()
[task 2024-03-09T14:22:37.401Z] 14:22:37 INFO - File "/builds/worker/checkouts/gecko/third_party/python/requests/requests/models.py", line 1021, in raise_for_status
[task 2024-03-09T14:22:37.401Z] 14:22:37 INFO - raise HTTPError(http_error_msg, response=self)
[task 2024-03-09T14:22:37.401Z] 14:22:37 INFO - requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://hg.mozilla.org/l10n-central/ja/json-rev/e6c3fe91a9702d15ff37ce5b447d5a41629965b1
https://hg.mozilla.org/l10n-central/ja/json-rev/e6c3fe91a9702d15ff37ce5b447d5a41629965b1 reads
{
"error": "filtered revision 'e6c3fe91a9702d15ff37ce5b447d5a41629965b1' (not in 'replicatedserved' subset)"
}
A replication issue similar to Bug 1884332?
Japanese builds are likely busted on beta and central (= Nightly) until the issue has been resolved. It is unknown if a new commit would mitigate the issue.
| Comment hidden (Intermittent Failures Robot) |
|
||
Comment 2•1 year ago
|
||
It is unknown if a new commit would mitigate the issue.
Is it still busted? l10n-central/ja already has a couple additional commits, so it should be easy to check
https://hg.mozilla.org/l10n-central/ja
The problem is understanding how many of the other locales have issues.
|
|
||
Comment 3•1 year ago
|
||
Actually, the first URL now shows data instead of the error, so we already know that a new commit fixed it.
|
|
||
Comment 4•1 year ago
|
||
Not sure if this is the best approach (should I check for a JSON with error in it instead of checking the status code?), but I don't see any error
import requests
def extract_changesets(url):
changesets = []
try:
r = requests.get(url)
data = r.json()
for loc, loc_data in data.items():
changesets.append(f"{loc}:{loc_data['revision']}")
except Exception as e:
print(e)
return changesets
def check_changesets(url):
changesets = extract_changesets(url)
for c in changesets:
loc, changeset = c.split(":")
try:
print(loc, end=" ", flush=True)
url = f"https://hg.mozilla.org/l10n-central/{loc}/json-rev/{changeset}"
r = requests.get(url)
if r.status_code == 404:
print(f"\n{url}: {e}")
except Exception as e:
print(e)
print("\nChecking mozilla-beta changesets")
check_changesets(
"https://hg.mozilla.org/releases/mozilla-beta/raw-file/default/browser/locales/l10n-changesets.json"
)
print("\nChecking mozilla-central changesets")
check_changesets(
"https://hg.mozilla.org/mozilla-central/raw-file/default/browser/locales/l10n-changesets.json"
)
| Comment hidden (Intermittent Failures Robot) |
|
||
Comment 6•1 year ago
|
||
This was a side effect of the hg server issues experienced the last few weeks. When this happens on a single-headed repo the easiest solution is to make a new push, as we've seen here. Sorry for the inconvenience.
Description
•