-
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Set up CI for Windows with Azure Pipelines #120
Conversation
Now we have got CI build for Windows. It still seems to be unstable by puppeteer/puppeteer#1947 but it would be better than shipping release with bugs. |
It is better to run CI in each commit than using |
Use fixed directory path to Carlo profile and omit cleanup.
Override close function of Window to ignore raising an error if a target page has already closed.
try { | ||
return await close.call(win) | ||
} catch (e) { | ||
if (!e.message.includes('Target closed.')) throw e |
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.
Even if raising error Target closed.
, the close
event has called correctly. We decided to ignore this error.
this.carloInternal = await carlo.launch({ | ||
localDataDir, | ||
localDataDir: path.resolve(os.tmpdir(), './marp-cli-carlo'), |
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.
Update the temporary directory to use a fixed path to prevent random failing when finalization.
Resolves #119.
CircleCI is still primary CI service for Marp team. Azure Pipelines will be used only for testing in Windows environment.