Test of 512 bits key is failed after upgrading openssl-1.0.1o due to
its limit of 768 bits key size. Remove it and start from 1024 bits
test.

Reviewed-By: Michael Dawson <mdawson@devrus.com>
PR-URL: #25533

This is a minimal effort to support test output written both to
stdout and file in order to get our buildbots understanding
test output.

Cherry picked from jbergstroem/node@3194073
Original commit metadata follows:
  PR-URL: nodejs/node#934
  Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com>
  Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>

Snapshots speed up start-up by a few milliseconds but are potentially
dangerous because of the fixed hash seed that is used for strings and
dictionaries, making collision denial-of-service attacks possible.

Release builds on iojs.org have snapshots disabled but source builds
did not, until now.

The risk for individual source builds is low; the binary gets a random
32 bits hash seed that should be hard to guess by an external attacker.

It's when binaries are distributed by, for example, a distro vendor
that the fixed hash seed becomes a vulnerability, because then it's
possible to target a large group of people at once.

People that really need the faster start-up time can use the new
--with-snapshot configure flag.

Cherry picked from bnoordhuis/io.js@4f68369
Original commit metadata below:
  PR-URL: nodejs/node#585
  Reviewed-By: Bert Belder <bertbelder@gmail.com>
  Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
  Reviewed-By: Rod Vagg <rod@vagg.org>

On a few of our installations (namely CentOS), passing 'INFO'
resulted in a silent loglevel. Use a logging constant instead.

Cherry-picked from nodejs/node@8606793
Original commit metadata follows:
  Fixes: nodejs/build#104
  PR-URL: nodejs/node#1842
  Reviewed-By: Rod Vagg <rod@vagg.org>

Since we will run linting before compiling or testing there's no
need to run it as part of the ci testing.

Cherry-picked from nodejs/node@8d8a26e
Original commit metadata follows:
  PR-URL: nodejs/node#1965
  Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
  Revewied-By: Evan Lucas <evanlucas@me.com>

There is now a sepearate linter job taking care of
running jslint.

See nodejs/node#2004