| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
I feel really really silly that I listed that in the last release but didn't actually have it.. Maybe say - (Mistakenly missing from v5.4.0) below that line? |
Sorry, something went wrong.
|
Also could you fix that url shortening so it is #3622 instead of node#3622? |
Sorry, something went wrong.
Sorry, something went wrong.
not ok 81 test-net-pipe-connect-errors.js # fs.js:1045 # return binding.chmod(pathModule._makeLong(path), modeNum(mode)); # ^ # # Error: ENOENT: no such file or directory, chmod '/home/iojs/build/workspace/node-test-binary-arm/RUN_SUBSET/addons/nodes/pi1-raspbian-wheezy/test/tmp.0/test.sock' # at Error (native) # at Object.fs.chmodSync (fs.js:1045:18) # at Server.<anonymous> (/home/iojs/build/workspace/node-test-binary-arm/RUN_SUBSET/addons/nodes/pi1-raspbian-wheezy/test/parallel/test-net-pipe-connect-errors.js:71:8) # at Server.g (events.js:260:16) # at emitNone (events.js:67:13) # at Server.emit (events.js:166:7) # at emitListeningNT (net.js:1263:10) # at nextTickCallbackWith1Arg (node.js:463:9) # at process._tickCallback (node.js:385:17) # at Function.Module.runMain (module.js:431:11) |
Sorry, something went wrong.
|
Arm-fanned job is running again https://ci.nodejs.org/job/node-test-commit-arm-fanned/1046/ edit: Looks like that failure is consistent. edit: ran on v5.4.0 and also had failure. edit: ran on v5.3.0 and there are no failures |
Sorry, something went wrong.
|
@jbergstroem Any idea what the issue might be with the above CI failure? I want to rule out a problem with CI passing in environment variables or whatever before I look at the code (which I can't do until later anyway...) |
Sorry, something went wrong.
|
Looks like it fails with the code reverted as well but fails differently? Woot, sort of, I guess... |
Sorry, something went wrong.
|
I'm mostly finding it super odd how v5.3 passes, v5.4 / 5.4.1 fails, but master passses WUT |
Sorry, something went wrong.
|
@jbergstroem has attempted to change something in CI. Running again to see if it is fixed --> https://ci.nodejs.org/job/node-test-commit-arm-fanned/1056/ |
Sorry, something went wrong.
|
The above test had an unrelated failure (well unrelated to past failures). Running the full CI one more time because |
Sorry, something went wrong.
|
so, he latest arm fails is because the build volume is mounted in a different folder than the temp directory; i'll look at fixing that locally. so; "expected fail would pass" |
Sorry, something went wrong.
|
..and as for windows, we have a slave connection issue. Current state looks good to me. |
Sorry, something went wrong.
|
One more time: https://ci.nodejs.org/job/node-test-pull-request/1202/ |
Sorry, something went wrong.
|
✅ full green! |
Sorry, something went wrong.
|
@nodejs/build @Fishrock123 did we get ssh keys for the new release team members on to the server in ~dist yet? I'm catching up now but this is required in order for @thealphanerd to get this released and I haven't seen a discussion about that. |
Sorry, something went wrong.
|
Running CITGM: https://ci.nodejs.org/job/thealphanerd-smoker/28/ |
Sorry, something went wrong.
|
@nodejs/build Uh oh, I don't think so. I was going to do it alongside adding the keys to the readme, but those were merged so fast I didn't get to look at them and forgot about it... |
Sorry, something went wrong.
|
The test suite for tape is failing on fedora 23. Rerunning for 5.4.0 to see if this is new |
Sorry, something went wrong.
General improvements to crypto.markdown including new and revised examples. PR-URL: #4435 Reviewed-By: Fedor Indutny <fedor@indutny.com> Reviewed-By: Shigeki Ohtsu <ohtsu@iij.ad.jp>
PR-URL: #4549 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Adds Myles Borins and his public key to the README PR-URL: #4578 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
Adds Evan Lucas and his public key to the README for releases PR-URL: #4579 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>
It avoids the creation of unnecessary handles. This issue is causing intermitent failures in `test-cluster-disconnect-race` on `FreeBSD` and `OS X`. The problem is that the `worker2.disconnect` is being called on the master before the `queryServer` is handled, causing the worker to be deleted, then the Server handle is created afterwards. Later on, when `removeWorker` is called from the `exit` handler, there are no workers left, but one handle, thus the `AssertionError`. Add a new `test/sequential/test-cluster-disconnect-leak` based on `test-cluster-disconnect-race` that creates lots of workers and fails consistently without this patch. PR-URL: #4465 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Rich Trott <rtrott@gmail.com>
fix description about the latest LTS release download page to make it clear PR-URL: #4583 Reviewed-By: Rod Vagg <rod@vagg.org> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
A few tests in test/gc include the http module twice. Remove duplicate require(). PR-URL: #4606 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Michaël Zasso <mic.besace@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
The exts and trailingSlash variables are only used if the path isn't cached. This commit moves them further down in the code, and changes from var to const. PR-URL: #3579 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Two tests were requiring the common module twice. This removes the duplicate require statement in the tests. PR-URL: #4611 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: James M Snell <jasnell@gmail.com>
Remove redeclarations of variables in node.js. This includes removing
one apparently unnecessary `NativeModule.require('module')`.
PR-URL: #4605
Reviewed-By: Brian White <mscdex@mscdex.net>
Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
Reviewed-By: James M Snell <jasnell@gmail.com>
In lib/_http_client.js, the variable `conn` was declared with the `var` keyword three times in the same scope. This change eliminates the variable entirely. PR-URL: #4612 Reviewed-By: Michaël Zasso <mic.besace@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
In order to make developers aware of node-core built-in functionality, which might replace module APIs, we should add an example of readline`s interface usage. SEO will eventually aid this goal, since it is well searched on Q&A sites. PR-URL: #4609 Reviewed-By: Roman Reiss <me@silverwind.io> Reviewed-By: James M Snell <jasnell@gmail.com>>
Do not attempt to read data from the socket whilst on OpenSSL's stack, weird things may happen, and this is most likely going to result in some kind of error. PR-URL: #4624 Reviewed-By: Trevor Norris <trev.norris@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
This comment was added with an assumption that we could determine the IP address that localhost should resolve to without performing a lookup. This was a false assumption and should be removed. PR-URL: #4648 Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
`fork` is imported twice in a row. Remove duplication. PR-URL: #4634 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Brian White <mscdex@mscdex.net> Reviewed-By: Michaël Zasso <mic.besace@gmail.com>
|
Rebase against v5.x to get backported v8 fix. Added two new commits from master. Backed out commit for arrow functions to see if that was what was breaking fedora 23 on citgm. CI: https://ci.nodejs.org/job/node-test-pull-request/1206/ edit: CI failures on PPC appear to all be timeout related, I'm going to write them off as unrelated |
Sorry, something went wrong.
|
One more CI run before the Build group meeting. will cut release after assuming all green https://ci.nodejs.org/job/node-test-pull-request/1207/ edit: @mhdawson can you look at the PPC failures we are getting here. What is causing these timeouts? |
Sorry, something went wrong.
|
Running release job: https://ci.nodejs.org/job/iojs+release/339/ |
Sorry, something went wrong.
|
@thealphanerd which key was used to sign this release? The new key from #4657? |
Sorry, something went wrong.
|
@Starefossen this one was signed by @Fishrock123 on behalf of @thealphanerd, so you can go ahead without any change for Docker for now and it should be fine. $ git tag -v v5.4.1
object ff992037246010fdad6f72323fe556da69640531
type commit
tag v5.4.1
tagger Jeremiah Senkpiel <fishrock123@rocketmail.com> 1452641853 -0500
2016-01-12 Node.js v5.4.1 (Stable) Release
gpg: Signature made Wed 13 Jan 10:37:43 2016 AEDT using RSA key ID 813DAE8E
gpg: Good signature from "keybase.io/fishrock <fishrock@keybase.io>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: FD3A 5288 F042 B685 0C66 B31F 09FE 4473 4EB7 990E
Subkey fingerprint: 50CB D045 6807 04B1 B723 6935 45F5 EEBD 813D AE8E
$ curl https://nodejs.org/download/release/v5.4.1/SHASUMS256.txt.asc | gpg
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3371 100 3371 0 0 4421 0 --:--:-- --:--:-- --:--:-- 4418
c523472a5972823e8b6baf2419f837885321c772612ec508a65614c758e25a46 node-v5.4.1-darwin-x64.tar.gz
c4c721d7ef2fba4e5b21dfc8017bda10c8a4d8ff322f7545e74943ca9828ee89 node-v5.4.1-darwin-x64.tar.xz
fd91d8fcbe72c76d1e58ddb3ba8bc08073c8c1e6d595bfe4b8b22e9b92855ed7 node-v5.4.1-headers.tar.gz
17424fc015dc668480537fd32f67f4d85d6e78e37f87d5eef58ef12d40bcd335 node-v5.4.1-headers.tar.xz
362ae4539b6be075b6757ba689f0ae522cfc9340c81061aca880f92fce9595c7 node-v5.4.1-linux-arm64.tar.gz
40f8e6485759a5c5f166745f7d8f33285ef425d2fe569d085220fd954fb790b9 node-v5.4.1-linux-arm64.tar.xz
21617e86758f1f95a3b9444be965aa87907410d786529cfd6aa2169ab7b5e15b node-v5.4.1-linux-armv6l.tar.gz
2698fdd1bcfb2234f65b786c0a46ac29bf2c301c992fd72045fd03553a57e298 node-v5.4.1-linux-armv6l.tar.xz
af36dff32934dea9446673a5453efcda6e4621ce7fa73e0a401f1444c2f929af node-v5.4.1-linux-armv7l.tar.gz
09b346ee665e3510fe8679df95bc32e8dda5953e05807c21816a25b9f5969dd4 node-v5.4.1-linux-armv7l.tar.xz
1880f3421da5579678803a523c314b345f5db00799b51b7fd9484a3248efc068 node-v5.4.1-linux-x64.tar.gz
9d264641df98742246bfd868e84cf98f649077f31eeae58931a31b0b5eee05a0 node-v5.4.1-linux-x64.tar.xz
184790d2ec8f95a75e7e746b3007e848aeba91be14ad7cec415b425df0df92e5 node-v5.4.1-linux-x86.tar.gz
a18707f7ac559563220e3319f251a2a5479b8445538f757df3a6c2dead007f1b node-v5.4.1-linux-x86.tar.xz
059aae464e48cc11c5af1a12f47e6859da28b0fcf794f5c33d14ab7235fee1db node-v5.4.1.pkg
956b3b0790b5742765966c6851e43c6fca298ecfb8c7102fd87e5fb6294bebd4 node-v5.4.1-sunos-x64.tar.gz
5644e5998d58bfac337a7c8672de68ec0a6dc55366a098b2364b9fbad6b345d8 node-v5.4.1-sunos-x64.tar.xz
a3eb11d58760b4b9007ac882c02e7608549fe7f65124ca90a387ba71c524b3e2 node-v5.4.1-sunos-x86.tar.gz
b8e78738f2714e34705eebd207400af422cee0842e7c599ab5077a4e51ed8453 node-v5.4.1-sunos-x86.tar.xz
78455ef2e3dea06b7d13d393c36711009048a91e5de5892523ec4a9be5a55e0c node-v5.4.1.tar.gz
4e7d3fdfeac85c46ddaef0224695620f218e7a178e97d6e210d6d643483f1d53 node-v5.4.1.tar.xz
a65a1eaeb1bd234516232803839ef5a2f6526730abfef98724c103f76a8b5440 node-v5.4.1-x64.msi
d06e7a697d7519b83dbaf631ad45103f8768f6bfef13fa3ce8bddba9d9f436f2 node-v5.4.1-x86.msi
85311ba0ce30a6f41c6d677c33f4c198e3a3f4a4e62754a84c6c3036a1fc6e4f win-x64/node.exe
e2715e5383d61c67d4f7d41f1fc760ef311c89b365b931720a452f1409ccabb4 win-x64/node.lib
3edae51060629596c592e2bee4da15a4b3f7e36f0cb80c8a2fd6eedcefd0de13 win-x86/node.exe
0dbb491180a380170bb89dc6976207c96c50aaf849021c7b049065c169fd09ef win-x86/node.lib
gpg: Signature made Wed 13 Jan 10:45:09 2016 AEDT using RSA key ID 813DAE8E
gpg: Good signature from "keybase.io/fishrock <fishrock@keybase.io>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: FD3A 5288 F042 B685 0C66 B31F 09FE 4473 4EB7 990E
Subkey fingerprint: 50CB D045 6807 04B1 B723 6935 45F5 EEBD 813D AE8E
|
Sorry, something went wrong.
PR-URL: nodejs#86 Related: nodejs/node#4626 Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@dnt.no>
PR-URL: docker-library#1336 Related: nodejs/node#4626 Related: nodejs/docker-node#86 Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@dnt.no>
PR-URL: docker-library#1337 Related: nodejs/node#4626 Related: nodejs/docker-node#86 Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@dnt.no>
Notable Changes: * Minor performance improvements: - module: move unnecessary work for early return (Andres Suarez) nodejs#3579 * Various bug fixes * Various doc fixes * Various test improvements PR-URL: nodejs#4626 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
PR-URL: docker-library#1337 Related: nodejs/node#4626 Related: nodejs/docker-node#86 Signed-off-by: Hans Kristian Flaatten <hans.kristian.flaatten@dnt.no>
| Back | FazBrowse Home | New Git URL |
Notable Changes
Known issues
commits