Closed
Bug 552365
Opened 15 years ago
Closed 15 years ago
Test plugin is not present on test machines
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: roc, Assigned: ted)
Details
Attachments
(1 file)
|
742 bytes,
patch
|
catlee
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
E.g.
http://tinderbox.mozilla.org/showlog.cgi?lohttp://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1268620304.1268622921.937.gzg=Firefox/1268620304.1268622921.937.gz
REFTEST TEST-KNOWN-FAIL | file:///builds/moz2_slave/mozilla-central-linux-debug-unittest-reftest/build/reftest/tests/modules/plugin/test/reftest/plugin-sanity.html |
That's from the test
fails-if(!haveTestPlugin) == plugin-sanity.html div-sanity.html
!haveTestPlugin is true on all test machines currently, it seems. I don't know how long this had been going on.
I'm not sure if this is Build Config or Releng, or something else...
| Reporter | ||
Comment 1•15 years ago
|
||
Note, the test plugin seems to be there OK on the try servers, just not on trunk Tinderbox.
| Reporter | ||
Updated•15 years ago
|
Component: Build Config → Release Engineering
Product: Core → mozilla.org
QA Contact: build-config → release
Version: Trunk → other
| Reporter | ||
Comment 2•15 years ago
|
||
Given that things seem to be OK on the try-server, I'm guessing this must be Releng.
Comment 3•15 years ago
|
||
The test plugin seems to be packaged for tests in testing/mochitest/Makefile.in; did something change so the split-out reftest runs no longer extract that? Or did they never extract it, and it just happens to work if the slave has previously run Mochitests and bits are leftover?
Comment 4•15 years ago
|
||
Better log url:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1268620304.1268622921.937.gz
Note that the try server runs unit tests in the tree they're built in, while m-c runs them using packaged build/tests/symbols.
I see bin/plugins/libnptest.so being unpacked out of the tests archive, as well as several files in mochitest/browser/toolkit/mozapps/plugins/.
Comment 5•15 years ago
|
||
(In reply to comment #3)
The different test jobs all run in their own directory, so there's no chance of that type of cross talk. They unpack the full tests archive regardless of the subset they may actually use.
| Assignee | ||
Comment 6•15 years ago
|
||
I guess this has just never worked? That's kind of sad. Simple fix: add the --extra-profile-file to the runreftest.py call, like mochitest has:
http://hg.mozilla.org/build/buildbotcustom/file/tip/steps/unittest.py#l503
| Assignee | ||
Comment 7•15 years ago
|
||
I guess I was too thorough in bug 473935, since that conveniently masked these failures by making them KNOWN-FAIL.
| Assignee | ||
Comment 8•15 years ago
|
||
This should fix it, although I haven't tested the patch.
Updated•15 years ago
|
Attachment #432532 -
Flags: review?(catlee) → review+
Comment 9•15 years ago
|
||
Comment on attachment 432532 [details] [diff] [review]
simple fix
changeset: 648:707481400567
Landing this today.
Attachment #432532 -
Flags: checked-in+
Comment 10•15 years ago
|
||
seems to have landed ok.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•