Skip to content
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

Introduce --ignore_compile_failure to build script #1205

Merged
merged 1 commit into from
Oct 1, 2018

Conversation

simonhong
Copy link
Member

@simonhong simonhong commented Sep 20, 2018

This option compiles files as many as possible regardless of compile error.
It would be useful when we trigger full build before going to bed.

Close #1204

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Verified that these changes build without errors on
    • Windows
    • macOS
    • Linux
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests) on
    • Windows
    • macOS
    • Linux
  • Ran git rebase master (if needed).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Requested a security/privacy review as needed.

Test Plan:

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions.

@simonhong simonhong self-assigned this Sep 20, 2018
@simonhong simonhong requested a review from bridiver September 20, 2018 07:53
@simonhong simonhong force-pushed the ignore_compile_failure branch from d3b5b79 to 44efa8e Compare September 26, 2018 23:57
This option compiles files as many as possible regardless of compile error.
It would be useful when we trigger full build before going to bed.
@simonhong simonhong force-pushed the ignore_compile_failure branch from 44efa8e to e214c6f Compare September 26, 2018 23:58
@simonhong simonhong requested a review from emerick September 27, 2018 00:48
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -187,9 +187,13 @@ const util = {

if (process.platform === 'win32') util.updateOmahaMidlFiles()

let num_compile_failure = 1
if (config.ignore_compile_failure)
num_compile_failure = 1000
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe we want to allow more than 1k? I'm thinking chromium rebase sometimes might surpass since 1 real error can be much more. Merging in any case though.

@bbondy bbondy added this to the 1.1 (0.57.x) milestone Oct 1, 2018
@bbondy bbondy merged commit d95374b into master Oct 1, 2018
@bbondy bbondy removed this from the 0.57.x - Dev milestone Oct 17, 2018
@simonhong simonhong deleted the ignore_compile_failure branch October 30, 2018 01:09
@bbondy bbondy removed the 0.57.x label Jan 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants