benchmark: remove dependency on unshipped tools by AdamMajer · Pull Request #51146 · nodejs/node
AdamMajer
changed the title
test: remove dependency on unshipped tools
benchmark: remove dependency on unshipped tools
tools/node_modules is removed from the tarball so it should not be used as part of unit tests or benchmarks. Fixes: nodejs#51145 Refs: nodejs#50684
jasnell pushed a commit that referenced this pull request
Dec 25, 2023RafaelGSS pushed a commit that referenced this pull request
Jan 2, 2024AdamMajer added a commit to AdamMajer/node that referenced this pull request
Feb 13, 2024In previous version of this fix, I've simply added a check if the tested tool is available or not. Unfortuntelly, this fails when only the first tool is to be run as part of the test-benchmark-misc, and it doesn't exist. benchmark/test-benchmark-misc ... AssertionError [ERR_ASSERTION]: benchmark file not running exactly one configuration in test: ... misc/startup-cli-version.js ... The solution is to move the tool that is not present in a tarball down the list. Fixes: nodejs#51146 Refs: nodejs#50684
AdamMajer added a commit to AdamMajer/node that referenced this pull request
Feb 13, 2024In previous version of this fix, I've simply added a check if the tested tool is available or not. Unfortuntelly, this fails when only the first tool is to be run as part of the test-benchmark-misc, and it doesn't exist. benchmark/test-benchmark-misc ... AssertionError [ERR_ASSERTION]: benchmark file not running exactly one configuration in test: ... misc/startup-cli-version.js ... The solution is to move the tool that is not present in a tarball down the list. Fixes: nodejs#51146
AdamMajer added a commit to AdamMajer/node that referenced this pull request
Feb 13, 2024In previous version of this fix, I've simply added a check if the tested tool is available or not. Unfortuntelly, this fails when only the first tool is to be run as part of the test-benchmark-misc, and it doesn't exist. benchmark/test-benchmark-misc ... AssertionError [ERR_ASSERTION]: benchmark file not running exactly one configuration in test: ... misc/startup-cli-version.js ... The solution is to move the tool that is not present in a tarball down the list. Refs: nodejs#51146
AdamMajer added a commit to AdamMajer/node that referenced this pull request
Feb 14, 2024In previous version of this fix, I've simply added a check if the tested tool is available or not. Unfortuntelly, this fails when only the first tool is to be run as part of the test-benchmark-misc, and it doesn't exist. benchmark/test-benchmark-misc ... AssertionError [ERR_ASSERTION]: benchmark file not running exactly one configuration in test: ... misc/startup-cli-version.js ... One solution is to check if the cli tool is actually available before using it in a benchmark Refs: nodejs#51146
richardlau pushed a commit that referenced this pull request
Mar 25, 2024aduh95 pushed a commit that referenced this pull request
May 11, 2024targos pushed a commit that referenced this pull request
May 11, 2024marco-ippolito pushed a commit that referenced this pull request
Jun 17, 2024marco-ippolito pushed a commit that referenced this pull request
Jun 17, 2024marco-ippolito pushed a commit that referenced this pull request
Jun 17, 2024sophoniie pushed a commit to sophoniie/node that referenced this pull request
Jun 20, 2024PR-URL: nodejs#51746 Refs: nodejs#51146 Refs: nodejs#50684 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
bmeck pushed a commit to bmeck/node that referenced this pull request
Jun 22, 2024PR-URL: nodejs#51746 Refs: nodejs#51146 Refs: nodejs#50684 Reviewed-By: Richard Lau <rlau@redhat.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters