Comparing changes
Open a pull request
base repository: nodejs/node-v0.x-archive
base: 440b9e224574
head repository: nodejs/node-v0.x-archive
compare: b5f9779c2f83
- 15 commits
- 235 files changed
- 2 contributors
Commits on Feb 25, 2014
-
test: remove next-tick-loops-quick
Scheduling of next ticks from within the next tick handler will result in a tight execution loop where a timer cannot break into. This test was invalid
-
test: pummel fs-watch-file-slow handle spurious
watch file will now generate an empty event when the file doesn't exist initially
-
test: pummel/test-net-throttle adhere to streams
bufferSize is now a getter that shows all that has not been acknowledged by the os, as well as in the buffer state. The test is only looking to verify the js verified state.
-
test: move pummel/test-fs-largefile to disabled
This test is particularly pathological, and requires a ton of time to run, we need to find a better way to manage it but in general this path is fairly safe these days.
-
test: internet/test-dns handle ESERVFAIL
ESERVFAIL is also an acceptable error code when failing to resolve a domain.
-
test: pummel/*ci-reneg* handle EPIPE
When calling out to the openssl client handle the child closing and returning EPIPE on writes
-
-
-
-
-
-
test: pummel/net-connect-econnrefused backoff
We were trying too hard to connect, and getting timeouts instead of the refusals, slow down how hard we try.
-
test: internet/test-dns disable implicit ipv6
This ends up being too difficult to test across different deployments
-
net: fix listening on FDs on Windows
Fix a bug introduced by 3da36fe of a missed early return of a handle that needed to be passed to listen. Fixes test-net-listen-fd0.js on Windows
-
windows: fix module registration
The linker was optimizing the static variables that were supposed to trigger module initialization. I am making them non-static, and dllexport so that they don't get optimized away. Fixes #7116
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 440b9e224574...b5f9779c2f83