mirror of
https://github.com/nodejs/node.git
synced 2024-12-01 16:10:02 +01:00
fed0b28754
Per the discussion on #2471, the JS symbols checked for by this test were occasionally too deep in the stack and were being ignored by the tick processor. I have addressed this by increasing the stack depth inspected by the tick processor and looking for the eval symbol which is more likely to be present. Additional flakiness was caused by occasional misses of the code creation event for the JS function being executed. I now have separate code snippets to test for JS and C++ symbols and if the code creation event is missed for the JS symbol test then I check for a percentage of UNKNOWN symbols in processed output. This is considered a success as the processing scripts in the node repository are still correctly processing the ticks recieved from the v8 scripts. Further investigation is needed into the v8 profiling scripts to determine why code creation events are being missed. PR-URL: https://github.com/nodejs/node/pull/2694 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
26 lines
744 B
Plaintext
26 lines
744 B
Plaintext
prefix parallel
|
|
|
|
# To mark a test as flaky, list the test name in the appropriate section
|
|
# below, without ".js", followed by ": PASS,FLAKY". Example:
|
|
# sample-test : PASS,FLAKY
|
|
|
|
[true] # This section applies to all platforms
|
|
|
|
[$system==win32]
|
|
test-tls-ticket-cluster : PASS,FLAKY
|
|
|
|
[$system==linux]
|
|
test-cluster-worker-forced-exit : PASS,FLAKY
|
|
test-http-client-timeout-event : PASS,FLAKY
|
|
test-tls-no-sslv3 : PASS,FLAKY
|
|
test-child-process-buffering : PASS,FLAKY
|
|
test-child-process-exit-code : PASS,FLAKY
|
|
|
|
[$system==macos]
|
|
|
|
[$system==solaris] # Also applies to SmartOS
|
|
test-debug-signal-cluster : PASS,FLAKY
|
|
|
|
[$system==freebsd]
|
|
test-net-socket-local-address : PASS,FLAKY
|