Closed
Bug 1035580
Opened 12 years ago
Closed 12 years ago
Unit tests failing on Mac with current Master build
Categories
(Hello (Loop) :: Server, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 1032733
People
(Reporter: jbonacci, Unassigned)
Details
(Whiteboard: [qa+])
This is all very new and not related to the errors I see on Linux in bug 1029751
I built the last Master on my Mac.
I have Redis server running on the correct port:
"[35035] 07 Jul 18:51:33.470 # Server started, Redis version 2.6.14
[35035] 07 Jul 18:51:33.472 * DB loaded from disk: 0.002 seconds
[35035] 07 Jul 18:51:33.472 * The server is now ready to accept connections on port 6379"
etc...
Here is what I see now:
https://jbonacci.pastebin.mozilla.org/5531288
I am none too happy about the fatal exception.
Without the redis server running, I get cleaner, expected results.
| Reporter | ||
Updated•12 years ago
|
Whiteboard: [qa+]
Comment 1•12 years ago
|
||
I believe this is a duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1032733, you need to update the ulimit on your machine.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Comment 2•12 years ago
|
||
Bleh. I had done that.
OK. Let me take another look at my test setup and see what might have happened...
| Reporter | ||
Comment 3•12 years ago
|
||
Set the ulimit as follows:
ulimit -S -n 2048
and ran "make test"
Results are better - failures are now related to websockets.
Status: RESOLVED → VERIFIED
Comment 4•12 years ago
|
||
Could you try make travis to see if it fix your problem?
Comment 5•12 years ago
|
||
I also have updated the Makefile with a higher timeout so this may have fixed your problem.
| Reporter | ||
Comment 6•12 years ago
|
||
Yep. "make travis" instead of "make test" addressed the websocket failures.
We still need the ulimit change though...
Comment 7•12 years ago
|
||
The ulimit had been added to the docs. Are you thinking about something different?
| Reporter | ||
Comment 8•12 years ago
|
||
Nope. Sorry for the confusion.
You need to log in
before you can comment on or make changes to this bug.
Description
•