Closed Bug 1509294 Opened 6 years ago Closed 6 years ago

Perma ImportError: No module named util.retry

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P5)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: intermittent-bug-filer, Assigned: mtabara)

Details

(Keywords: intermittent-failure)

Filed by: rmaries [at] mozilla.com https://treeherder.mozilla.org/logviewer.html#?job_id=213361817&repo=mozilla-central https://queue.taskcluster.net/v1/task/Y9ag4PQNRfSU1ZNfnIqKcg/runs/0/artifacts/public/logs/live_backing.log 2018-11-22 12:05:34,781 - INFO - actions: [u'submit-locale'] 2018-11-22 12:05:34,785 - INFO - Servers: [u'nightly'] Traceback (most recent call last): File "/builds/scriptworker/py27venv/bin/balrogscript", line 11, in <module> sys.exit(main()) File "/builds/scriptworker/py27venv/lib/python2.7/site-packages/balrogscript/script.py", line 257, in main submit_locale(task, config, balrog_auth) File "/builds/scriptworker/py27venv/lib/python2.7/site-packages/balrogscript/script.py", line 84, in submit_locale from util.retry import retry # noqa: E402 ImportError: No module named util.retry exit code: 1
Summary: Intermittent ImportError: No module named util.retry → Perma ImportError: No module named util.retry
https://github.com/mozilla-releng/build-puppet/pull/304 landed today encompassing some great changes and refactoring in balrogscript via https://github.com/mozilla-releng/balrogscript/pull/40/. while puppet was still rolling out to the pools of (balrog)workers, some of the jobs in th nightly graph have just been happening with the old configurations. I rerun the failed jobs which all went green. This should be fixed now.
Assignee: nobody → mtabara
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.