confusing output from update test steps after switching to in tree mozharness

RESOLVED INCOMPLETE

Status

defect
RESOLVED INCOMPLETE
4 years ago
Last year

People

(Reporter: bhearsum, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

I was just grepping around for remaining uses of the old Mozharness repo in releases, and found that the new update tests (eg: http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/40.0b7-candidates/build1/logs/release-mozilla-beta-linux64_beta_update_tests_1-bm72-build1-build2.txt.gz) use archiver to get Mozharness (yay!) but they still repo scirpt_repo_url as the old Mozharness repo, eg:
release-mozilla-beta-win32_beta_update_tests_5-bm86-build1-build4.txt.gz:script_repo_url: https://hg.mozilla.org/build/mozharness
release-mozilla-beta-win32_beta_update_tests_5-bm86-build1-build4.txt.gz:TinderboxPrint: script_revlink: https://hg.mozilla.org/build/mozharness/rev/FIREFOX_40_0b7_RELEASE
Looks like this might be a more general thing for anything that uses ScriptFactory, I also see it in Fennec release repacks:
release-mozilla-beta-android-api-9_repack_2-bm71-build1-build9.txt.gz:script_repo_url: https://hg.mozilla.org/build/mozharness
release-mozilla-beta-android-api-9_repack_2-bm71-build1-build9.txt.gz:TinderboxPrint: script_revlink: https://hg.mozilla.org/build/mozharness/rev/FENNEC_40_0b6_RELEASE
I think this will solve this and other ScriptFactory cases.

<axe> bitrotted buildbot via bug 1180060 </axe>
Depends on: 1180060
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.