-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
update test-browser output folder #14384
update test-browser output folder #14384
Conversation
KarishmaGhiya
commented
Mar 19, 2021
•
edited
Loading
edited
- Making test browser output folder consistent [Test] browser test ouput folder consistency issue #8844
@HarshaNalluru Can you take a first look at this PR? |
"test:browser": "npm run clean && npm run build:test:browser && npm run unit-test:browser", | ||
"test:node": "npm run clean && npm run build:test:node && npm run unit-test:node", | ||
"test": "npm run test:node && npm run test:browser", | ||
"unit-test:browser": "", | ||
"unit-test:node": "npm run build:test:node && mocha --require source-map-support/register --reporter ../../../common/tools/mocha-multi-reporter.js --timeout 180000 --full-trace test-dist/index.node.js", | ||
"unit-test:node": "npm run build:test:node && mocha --require source-map-support/register --reporter ../../../common/tools/mocha-multi-reporter.js --timeout 180000 --full-trace \"test-dist/index.node.js\"", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"unit-test:node": "npm run build:test:node && mocha --require source-map-support/register --reporter ../../../common/tools/mocha-multi-reporter.js --timeout 180000 --full-trace \"test-dist/index.node.js\"", | |
"unit-test:node": "npm run build:test:node && mocha --require source-map-support/register --reporter ../../../common/tools/mocha-multi-reporter.js --timeout 180000 --full-trace \"dist-test/index.browser.js\"", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@KarishmaGhiya Can you fix the build failures?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
I am getting these errors - I'll check if there's an issue with Devops
Co-authored-by: Harsha Nalluru <[email protected]>
/azp run js - appconfiguration - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! This inconsistency has been around in our repo for ages. The changes all look good to me if CI passes.
Update ServiceBus.json (Azure#14384)