Closed
Bug 778133
Opened 14 years ago
Closed 14 years ago
Update mozbase in m-c for bug 776931
Categories
(Testing :: Mozbase, defect)
Testing
Mozbase
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla17
People
(Reporter: ahal, Unassigned)
References
Details
Attachments
(1 file)
|
45.10 KB,
patch
|
k0scist
:
review+
|
Details | Diff | Splinter Review |
Mozbase needs to be updated again for bug 776931. Jeff, you mentioned you wanted to get a few other changes in before it gets updated.. Are they minor/can be completed by early next week? This is blocking peptest from being run so I'd like to get it landed sooner rather than later.
Also there were two regressions in mozbase that broke peptest last time it was updated. As more and more harnesses are using it we need to be more careful. We really should be landing in m-i so at least we have backing out as a last line of defense. We should also be pushing to try and ideally have continuous integration on the git side. I'll file a separate bug about that.
| Reporter | ||
Updated•14 years ago
|
OS: Linux → All
Hardware: x86_64 → All
Comment 1•14 years ago
|
||
(In reply to Andrew Halberstadt [:ahal] from comment #0)
> Mozbase needs to be updated again for bug 776931. Jeff, you mentioned you
> wanted to get a few other changes in before it gets updated.. Are they
> minor/can be completed by early next week? This is blocking peptest from
> being run so I'd like to get it landed sooner rather than later.
We might as well go ahead and mirror now.
> Also there were two regressions in mozbase that broke peptest last time it
> was updated. As more and more harnesses are using it we need to be more
> careful. We really should be landing in m-i so at least we have backing out
> as a last line of defense. We should also be pushing to try and ideally have
> continuous integration on the git side. I'll file a separate bug about that.
+1 on landing in m-i. As said in bug 778140, we do have CI for mozbase and that wouldn't have caught this particular issue
| Reporter | ||
Comment 2•14 years ago
|
||
| Reporter | ||
Comment 3•14 years ago
|
||
The jetpack timeout and OSX leaks seem to happen on all the other tests. Though bug 746243 has introduced some new failures in peptest :(
| Reporter | ||
Comment 4•14 years ago
|
||
So due to bug 776931 peptest will also need to be updated. I'm going to do that here in one place to avoid any bustage since it is now unhidden for linux.
| Reporter | ||
Comment 5•14 years ago
|
||
Pushed to try yet again: https://tbpl.mozilla.org/?tree=Try&rev=d0120042a387
| Reporter | ||
Comment 6•14 years ago
|
||
Sorry, wrong link: https://tbpl.mozilla.org/?tree=Try&rev=1aa7c0a9117b
| Reporter | ||
Comment 7•14 years ago
|
||
All try failures are unrelated and setting noignore=1 shows that this also fixes the peptest bustage on windows and osx.
This is the exact patch that got submitted to try.
Could you give this a quick review and check it in Jeff? I'll update the git mozilla-central tags once it gets committed.
Attachment #648423 -
Flags: review?(jhammel)
Comment 8•14 years ago
|
||
I can't check in as I don't have push access for m-c. But I'll give you a review shortly
Comment 9•14 years ago
|
||
Comment on attachment 648423 [details] [diff] [review]
Sync mozbase and peptest to m-c
looks good
Attachment #648423 -
Flags: review?(jhammel) → review+
Updated•14 years ago
|
Keywords: checkin-needed
Comment 10•14 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/f36cf6866998
Andrew, please make sure that future patches you submit have all the needed hg commit information in them. You can find instructions at the link below. Thanks!
https://developer.mozilla.org/en/Creating_a_patch_that_can_be_checked_in
Flags: in-testsuite+
Keywords: checkin-needed
Comment 11•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla17
You need to log in
before you can comment on or make changes to this bug.
Description
•