-
-
Notifications
You must be signed in to change notification settings - Fork 32k
test: don't remove empty.txt on win32 #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: don't remove empty.txt on win32 #2
Conversation
on win32 we use empty.txt in the fixtures directory, otherwise we use a file constructed specifically for this test due to POSIX socket path length limitations, in which case we need to do appropriate cleanup
LGTM |
Another LGTM. |
@rvagg By the way, do you have commit rights? I'd like you to land your patches yourself. |
@bnoordhuis sure, is there anything special I need to know about the normal merge procedure? |
@rvagg Just the normal commit log as described in CONTRIBUTING.md plus PR-URL and Reviewed-By tags. Basically, what you see when you run |
on win32 we use empty.txt in the fixtures directory, otherwise we use a file constructed specifically for this test due to POSIX socket path length limitations, in which case we need to do appropriate cleanup Reviewed-By: Fedor Indutny <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]> PR-URL: #2
Original commit message: [bigint] Convert BigInt property names to decimal Hexadecimal/octal/binary BigInt property names should be converted to decimal, i.e. the following object literals should all be equivalent: var o = {0xF: 1}, p = {0xFn: 1}, q = {15: 1}, r = {15n: 1}. Test case by [email protected], uploaded at https://chromium-review.googlesource.com/c/v8/v8/+/3634937 Fixed: v8:10600 Change-Id: Ie1d8a16e95697cd31cbc0784843779c921ce91fa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3642302 Reviewed-by: Toon Verwaest <[email protected]> Commit-Queue: Jakob Kummerow <[email protected]> Cr-Commit-Position: refs/heads/main@{#80490} Refs: v8/v8@c875e86 PR-URL: nodejs#46501 Refs: v8/v8@c875e86 Reviewed-By: Michaël Zasso <[email protected]> Reviewed-By: Jiawen Geng <[email protected]>
Subtest nodejs#1, nodejs#2 of test-node-run.js originally matched the error message "Can't read package.json" on non-existent file. However, the subtests failed on Ubuntu20.04. we found that attempting to run a non-existent script like `node --run foo` using the latest version of node results in an error message like `Can't find “scripts” field in package.json` (on Ubuntu20.04, regardless of whether package.json is present in the subpath or not). So we modified the subtest so that if we match either of the two messages, the test passes.
Subtest nodejs#1, nodejs#2 of test-node-run.js originally matched the error message "Can't read package.json" on non-existent file. However, the subtests failed on Ubuntu20.04. we found that attempting to run a non-existent script like `node --run foo` using the latest version of node results in an error message like `Can't find “scripts” field in package.json` (on Ubuntu20.04, regardless of whether package.json is present in the subpath or not). So we modified the subtest so that if we match either of the two messages, the test passes.
🤖 Secure-PR-Guard AI Code ReviewAnalysis completed at: 2025-06-28 20:39:59 UTC 🟡 Risk Assessment: MEDIUM
🟢 Low Priority Issues
🔗 Powered by Secure-PR-Guard | 🛡️ OWASP LLM Top 10 Compliant This is an automated review. Please verify critical security findings manually. |
🤖 Secure-PR-Guard AI Code ReviewAnalysis completed at: 2025-06-28 21:19:12 UTC 🟡 Risk Assessment: MEDIUM
🟢 Low Priority Issues
🔗 Powered by Secure-PR-Guard | 🛡️ OWASP LLM Top 10 Compliant This is an automated review. Please verify critical security findings manually. |
Take 3: on win32 we use empty.txt in the fixtures directory, otherwise we use a file constructed specifically for this test due to POSIX socket path length limitations, in which case we need to do appropriate cleanup. Cleaning up empty.txt in fixtures causes downstream problems for other tests using it (currently the next test is test-zlib).