common/hexec: avoid brittle npm global size checks#14860
Conversation
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
|
Thanks, but I adjusted this to get e51e761 to pass. |
Fixes the current CI failure in
TestNPMGlobalInstalls.The test currently validates the global npm install path for PostCSS, Tailwind CSS, and Babel by asserting exact byte sizes for generated resources. That is brittle for globally installed npm packages: Tailwind output changed from the expected
CSS2 size: 4557|/css/main2.css|toCSS2 size: 4479|/css/main2.css|, while the integration itself still works.This failure is already present on
masterand is unrelated to #14841. It only blocks that PR operationally because CI is red on the shared branch.This change keeps the same integration coverage, but asserts stable success markers and resource paths instead of exact generated byte sizes.
Tests:
./check.sh ./common/hexec/..../check.shAI assistance disclosure: