1265177 - TEST-UNEXPECTED-FAIL | C:\slave\test\build\tests\mozmill\folder-display\test-tooltip-multimessage.js

Status: RESOLVED FIXED

(Thunderbird :: General, defect)

Description

[Jorg K (CEST = GMT+2)]

First seen 2016-04-16:

TEST-UNEXPECTED-FAIL | C:\slave\test\build\tests\mozmill\folder-display\test-tooltip-multimessage.js | test-tooltip-multimessage.js::test_tooltips
TEST-UNEXPECTED-FAIL | (runtestlist.py) | Exited with code 1 during directory run 

04:49:01     INFO -  SUMMARY-UNEXPECTED-FAIL | C:\slave\test\build\tests\mozmill\folder-display\test-tooltip-multimessage.js | test-tooltip-multimessage.js::test_tooltips
04:49:01     INFO -    EXCEPTION: Components.classes['@mozilla.org/embedcomp/default-tooltiptextprovider;1'] is undefined
04:49:01     INFO -      at: popup.xml line 533
04:49:01     INFO -         get_textProvider popup.xml:533 13
04:49:01     INFO -         fillInPageTooltip popup.xml:549 15
04:49:01     INFO -         test_tooltips test-tooltip-multimessage.js:42 3
04:49:01     INFO -         Runner.prototype.wrapper frame.js:585 9
04:49:01     INFO -         Runner.prototype._runTestModule frame.js:655 9
04:49:01     INFO -         Runner.prototype.runTestModule frame.js:701 3
04:49:01     INFO -         Runner.prototype.runTestDirectory frame.js:525 7
04:49:01     INFO -         runTestDirectory frame.js:707 3
04:49:01     INFO -         Bridge.prototype._execFunction server.js:179 10
04:49:01     INFO -         Bridge.prototype.execFunction server.js:183 16
04:49:01     INFO -         Session.prototype.receive server.js:283 3
04:49:01     INFO -         AsyncRead.prototype.onDataAvailable server.js:88 3

Looks like something changed in M-C to cause this, perhaps bug 1236991.

Comment 1

[aleth [:aleth]]

Attachment: Package TooltipTextProvider

Comment 2

[aleth [:aleth]]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=09b14130ab02

Comment 3

[Jorg K (CEST = GMT+2)]

Comment on attachment 8742128 [details] [diff] [review]
Package TooltipTextProvider

Review of attachment 8742128 [details] [diff] [review]:
-----------------------------------------------------------------

Stealing this review. We don't need to hold up proceedings for this simple change.
BTW, thanks a lot for investigating it.

Comment 4

[Jorg K (CEST = GMT+2)]

Comment on attachment 8742128 [details] [diff] [review]
Package TooltipTextProvider

Please don't call the patch files "."!!

Comment 5

[Jorg K (CEST = GMT+2)]

Thanks Aleth.
https://hg.mozilla.org/comm-central/rev/eb24f0689dcb

BTW, can you fix your try links. All the ones you post are invalid:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=09b14130ab02
Try clicking that. "try" is for Mozilla core.

Comment 6

[:Gijs (he/him)]

Good to see this got fixed so quickly. Hopefully build system work will obviate the need for package/installer manifests in future, they're a pain. :-\

(In reply to Jorg K (GMT+2) from comment #4)
> Comment on attachment 8742128 [details] [diff] [review]
> Package TooltipTextProvider
> 
> Please don't call the patch files "."!!

While I can't speak for Aleth with certainty, this is bzexport's default behaviour when submitting actual commits from your repo. It'd be lovely to have that fixed, but if I'm right this isn't human beings doing it on purpose or anything.

Comment 7

[aleth [:aleth]]

(In reply to :Gijs Kruitbosch from comment #6)
> > Please don't call the patch files "."!!
> 
> While I can't speak for Aleth with certainty, this is bzexport's default
> behaviour when submitting actual commits from your repo. It'd be lovely to
> have that fixed, but if I'm right this isn't human beings doing it on
> purpose or anything.

Yes, that's exactly what happens. There is a bzexport bug filed for this.

The try links are also not manually generated, and the extension doesn't seem to know try-c-c yet.

Comment 8

[Jorg K (CEST = GMT+2)]

So you're saying that there is some benefit to he had by doing things manually? ;-)