Nodejs/node
1
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-11-21 10:59:27 +00:00
Code Issues Actions 25 Packages Projects Releases Wiki Activity
62383cd113
node/test
History
Joyee Cheung 62383cd113 module: implement flushCompileCache() 
This implements an API for users to intentionally flush the
accumulated compile cache instead of waiting until process
shutdown. It may be useful for application that loads dependencies
first and then either reload itself in other instances, or spawning
other instances that load an overlapping set of its dependencies -
in this case its useful to flush the cache early instead of waiting
until the shutdown of itself.

Currently flushing is triggered by either process
shutdown or user requests. In the future we should simply start the
writes right after module loading on a separate thread, and this method
only blocks until all the pending writes (if any) on the other thread
are finished. In that case, the off-thread writes should finish long
before any attempt of flushing is made so the method would then only
incur a negligible overhead from thread synchronization.

PR-URL: https://github.com/nodejs/node/pull/54971
Fixes: https://github.com/nodejs/node/issues/54770
Fixes: https://github.com/nodejs/node/issues/54465
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
2024-09-20 19:05:07 +00:00
..
abort
addons test: merge ongc and gcutil into gc.js 2024-08-29 08:49:52 +01:00
async-hooks test: set test-writewrap as flaky 2024-09-06 17:02:29 -07:00
benchmark src,test: ensure that V8 fast APIs are called 2024-08-13 12:37:02 +00:00
cctest path: fix bugs and inconsistencies 2024-09-14 14:56:31 +00:00
common test: add platform timeout support for riscv64 2024-09-12 09:49:14 +09:30
doctool
embedding test: fix embedding test for Windows 2024-08-27 21:30:50 +00:00
es-module test: fix invalid wasm test 2024-09-20 10:42:59 +00:00
fixtures module: implement flushCompileCache() 2024-09-20 19:05:07 +00:00
fuzzers
internet
js-native-api node-api: add support for UTF-8 and Latin-1 property keys 2024-09-13 13:01:52 -07:00
known_issues vm: return all own names and symbols in property enumerator interceptor 2024-08-30 11:22:58 +00:00
message cli: ensure --run has proper pwd 2024-09-18 12:18:40 +00:00
node-api test: merge ongc and gcutil into gc.js 2024-08-29 08:49:52 +01:00
overlapped-checker
parallel module: implement flushCompileCache() 2024-09-20 19:05:07 +00:00
pseudo-tty
pummel test: refactor fs-watch tests due to macOS issue 2024-09-06 17:38:28 +00:00
report
sequential test: move test-http-max-sockets to parallel 2024-09-20 09:57:21 +00:00
testpy
tick-processor
tools
v8-updates
wasi
wasm-allocation
wpt test,crypto: update WebCryptoAPI WPT 2024-08-29 16:46:40 +00:00
eslint.config_partial.mjs
README.md doc, test: simplify test README table 2024-08-11 18:04:31 +00:00
root.status

README.md

Node.js Core Tests

This directory contains code and data used to test the Node.js implementation.

For a detailed guide on how to write tests in this directory, see the guide on writing tests.

On how to run tests in this directory, see the contributing guide.

For the tests to run on Windows, be sure to clone Node.js source code with the autocrlf git config flag set to true.

Test Directories

Directory Runs on CI Purpose
abort Yes Tests that use --abort-on-uncaught-exception and other cases where we want to avoid generating a core file.
addons Yes Tests for addon functionality along with some tests that require an addon.
async-hooks Yes Tests for async_hooks functionality.
benchmark Yes Test minimal functionality of benchmarks.
cctest Yes C++ tests that are run as part of the build process.
code-cache No Tests for a Node.js binary compiled with V8 code cache.
common N/A Common modules shared among many tests.1
doctool Yes Tests for the documentation generator.
es-module Yes Test ESM module loading.
fixtures N/A Test fixtures used in various tests throughout the test suite.
internet No Tests that make real outbound network connections.2
js-native-api Yes Tests for Node.js-agnostic Node-API functionality.
known_issues Yes Tests reproducing known issues within the system.3
message Yes Tests for messages that are output for various conditions
node-api Yes Tests for Node.js-specific Node-API functionality.
parallel Yes Various tests that are able to be run in parallel.
pseudo-tty Yes Tests that require stdin/stdout/stderr to be a TTY.
pummel No Various tests for various modules / system functionality operating under load.
sequential Yes Various tests that must not run in parallel.
testpy N/A Test configuration utility used by various test suites.
tick-processor No Tests for the V8 tick processor integration.4
v8-updates No Tests for V8 performance integration.

  1. Documentation ↩︎

  2. Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections. ↩︎

  3. All tests inside of this directory are expected to fail. If a test doesn't fail on certain platforms, those should be skipped via known_issues.status. ↩︎

  4. The tests are for the logic in lib/internal/v8_prof_processor.js and lib/internal/v8_prof_polyfill.js. The tests confirm that the profile processor packages the correct set of scripts from V8 and introduces the correct platform specific logic. ↩︎