Closed
Bug 444805
Opened 16 years ago
Closed 16 years ago
Pork: Figure out why testsuite fails
Categories
(Developer Infrastructure :: Source Code Analysis, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: taras.mozilla, Unassigned)
References
Details
Attachments
(1 file)
15.34 KB,
patch
|
Details | Diff | Splinter Review |
I wasn't aware i changed any pork code, so it's not amusing that it fails.
Will need to do some painful bisection(who came up with brilliant idea of using a bazillion repositories for coupled code).
Reporter | ||
Comment 1•16 years ago
|
||
elsa_tests.gen.incl.mk <-- this file is pure evil. Mainstream oink maintains a committed version of it that is older than the one we imported(this is something version control geeks can try to figure out). Neither oink, nor pork worked with an up-to-date file .
I disabled certain pointless tests, now the testsuite passes.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 2•16 years ago
|
||
would prefer a less drastic cut instead of
changeset 712 to allow "make check" to succeed.
Reporter | ||
Comment 3•16 years ago
|
||
(In reply to comment #2)
> Created an attachment (id=333409) [details]
> hg diff file oink/elsa_tests.gen.incl.mk
>
> would prefer a less drastic cut instead of
> changeset 712 to allow "make check" to succeed.
>
It's not drastic. Your proposed solution prevents the specific testcases from running..
My fix is that way it is because they are needed for parse testing with oink. qual was never intended to be run on them.
Updated•7 years ago
|
Product: Core → Firefox Build System
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•