Closed
Bug 1372239
Opened 7 years ago
Closed 3 years ago
Upgrade mozfile and mozinfo used in mozharness to be the latest mozbase versions
Categories
(Release Engineering :: Applications: MozharnessCore, enhancement)
Release Engineering
Applications: MozharnessCore
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: pmoore, Unassigned)
References
Details
This is a preliminary step to entirely removing the mozharness copies of these libraries. This first step will get us to the point of having two identical copies in-tree, such that afterwards we should be able to redirect mozharness to the canonical versions.
Reporter | ||
Comment 1•7 years ago
|
||
Try push in progress: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f9648466c2637617860bc82547a1e01aa5f735fe
Reporter | ||
Comment 2•7 years ago
|
||
I spoke with KWierso to ask how the results looked, and he said: 1) These are the things he is not sure of: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f9648466c2637617860bc82547a1e01aa5f735fe&exclusion_profile=false&duplicate_jobs=visible&filter-tier=1&filter-tier=2&filter-tier=3&group_state=expanded&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-classifiedState=unclassified&noautoclassify&selectedJob=106390406 2) He retriggered these jobs that might be masking other failures: https://treeherder.mozilla.org/#/jobs?repo=try&revision=f9648466c2637617860bc82547a1e01aa5f735fe&exclusion_profile=false&duplicate_jobs=visible&filter-tier=1&filter-tier=2&filter-tier=3&group_state=expanded&noautoclassify&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=pending&filter-resultStatus=running&filter-classifiedState=unclassified 3) He suggested maybe clipboard is having issues, and might be worth rebasing on mozilla-central to see if it is related to these changes, or the revision the changes were based on. I said I'll rebase on mozilla-central and see if I can run just the tests that are suspicious.
Reporter | ||
Comment 3•7 years ago
|
||
(In reply to Pete Moore [:pmoore][:pete] from comment #2) > 3) He suggested maybe clipboard is having issues, and might be worth > rebasing on mozilla-central to see if it is related to these changes, or the > revision the changes were based on. I said I'll rebase on mozilla-central > and see if I can run just the tests that are suspicious. https://treeherder.mozilla.org/#/jobs?repo=try&revision=8d229270dc83a3f06edcc5ba0568dde54de5b6ce&group_state=expanded&exclusion_profile=false&filter-tier=1&filter-tier=2&filter-tier=3
Comment 4•7 years ago
|
||
Hey Pete.. Sorry, when I asked you to do this I hadn't realized you already had the mozprocess patch done and tested. I think you're seeing the same clipboard issues I saw when I tried to do this a year ago (good to know they weren't because of mozprocess though!). I know this isn't really your domain, so feel free to drop it and maybe someone can pick it up again in the future.
Reporter | ||
Comment 5•7 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #4) > Hey Pete.. Sorry, when I asked you to do this I hadn't realized you already > had the mozprocess patch done and tested. I think you're seeing the same > clipboard issues I saw when I tried to do this a year ago (good to know they > weren't because of mozprocess though!). > > I know this isn't really your domain, so feel free to drop it and maybe > someone can pick it up again in the future. Thanks Andrew! Yeah, I think I'll do that, and drop work on this bug - so anyone else is free to pick this one up if they want. :)
Reporter | ||
Comment 6•3 years ago
|
||
Not actively working on this at the moment.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•