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

⚡️ Automated Leak Detection on CI ⚡️ #1464

Merged
merged 3 commits into from
Oct 10, 2015
Merged

⚡️ Automated Leak Detection on CI ⚡️ #1464

merged 3 commits into from
Oct 10, 2015

Conversation

samccone
Copy link
Member

@samccone samccone commented Oct 9, 2015

With this PR Drool is now providing us with the ability to fail CI when an implementation has memory leaks.

The perf tests are now run on every PR 👾 🍝

  1. Add automated leak detection ⛲
  2. Only run deploy code paths on deploy :) (faster test runs for everyone) 🐴
  3. Add some more compiled src ignores

@samccone samccone force-pushed the sjs/test-tweaks branch 5 times, most recently from f325150 to c1d64bb Compare October 9, 2015 03:53
@samccone
Copy link
Member Author

samccone commented Oct 9, 2015

🍏 CI is working (angular2 fails because of no routing)

https://travis-ci.org/tastejs/todomvc/builds/84436464

@samccone
Copy link
Member Author

samccone commented Oct 9, 2015

xref #1368

@ColinEberhardt
Copy link
Member

Wow, that is awesome! I'll definitely recommend using Drool to the developers where I work.

@passy
Copy link
Member

passy commented Oct 10, 2015

I love this! Just tested this with a few apps and it's sooo good! Thanks for this, @samccone!

passy added a commit that referenced this pull request Oct 10, 2015
⚡️ Automated Leak Detection on CI ⚡️
@passy passy merged commit 1365ef4 into master Oct 10, 2015
@passy passy deleted the sjs/test-tweaks branch October 10, 2015 21:17
return f === framework.name;
});
});
}
Copy link
Member

Choose a reason for hiding this comment

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

Missing semicolon, why didn't the linting process catch this?

Copy link
Member

Choose a reason for hiding this comment

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

Or me! Outrageous! Fixed in master with 1567e60.

Copy link
Member

Choose a reason for hiding this comment

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

Thanks @passy! Still we should check what's wrong with the linting tooling though.

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.

4 participants