enable necko unit tests on tinderboxes

RESOLVED WORKSFORME

Status

RESOLVED WORKSFORME
13 years ago
4 years ago

People

(Reporter: Biesinger, Unassigned)

Tracking

Details

from bug 304162

This probably only requires updating the tinderbox scripts; this should be
enabled by default (the setting is $NeckoUnitTest).

I think it'd be good to have this enabled on at least one tbox per platform, maybe:
btek (seamonkey)
monkey (seamonkey)
beast (firefox)

darin, does that list look good to you?
Assignee: dbaron → nobody

Comment 1

13 years ago
I updated the Tinderbox scripts yesterday, and we started getting the following
error when we tried to run the Necko unit tests:

Running Necko unit tests ...
Begin: Thu Aug 18 08:02:40 2005
cmd = necko_unit_tests/test_all.sh
End:   Thu Aug 18 08:02:41 2005
----------- Output from Necko unit tests ------------- 
  Can't exec "necko_unit_tests/test_all.sh": No such file or directory at
build-seamonkey-util.pl line 1420.
  Could not exec() at build-seamonkey-util.pl line 1421.
----------- End Output from Necko unit tests --------- 
Error: Necko unit tests exited with status 2
Error: Necko unit tests: exited with status 2

It seems that it isn't passing the full path to the test_all.sh script - we are
building in an objdir - not sure if that affects anything.
an objdir works for me... are you building a branch?

Comment 3

13 years ago
Nope - SeaMonkey trunk. See the AIX Laredo tinderbox on SeaMonkey-Ports.
oh. that compiles with --disable-tests. you should probably disable the tbox
tests in that case ;)

Updated

8 years ago
Component: Tinderbox Configuration → Tinderbox
Product: mozilla.org → Webtools
Ancient bug, I bet we are running these days.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

4 years ago
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.