aboutsummaryrefslogtreecommitdiffstats
path: root/Library/Homebrew/test/test_fails_with.rb
AgeCommit message (Collapse)Author
2014-08-31Rewrite fails_with tests as tests for CompilerFailureJack Nagel
2014-08-30Remove unnecessary empty blockJack Nagel
2014-08-30Test fails_with against spec objectsJack Nagel
2014-06-18Use a custom test class so we can avoid monkeypatchingJack Nagel
2014-06-12Make compiler objects directlyJack Nagel
2014-06-12No need to send, just call the methodJack Nagel
2013-12-12Add another fails_with testJack Nagel
2013-12-03Adjust fails_with syntax for non-Apple compilersMisty De Meo
The old version worked like this: fails_with :gcc => '4.8.1' That wasn't really flexible enough, and made it harder to distinguish different releases in the same GCC series. Since no one was really using it yet, this adjusts the syntax to be more similar to the Apple compilers: fails_with :gcc => '4.8' do release '4.8.1' end Like with Apple compilers, omitting `release` blacklists the entire series. This also unifies the `build` and `version` attributes and accessors, and exposes them under both names.
2013-09-01Implement fails_with for non-Apple compilersMisty De Meo
This adds support for non-Apple GCC compilers in the fails_with code. A fails_with block for a non-Apple compiler looks like: fails_with :gcc => '4.8.1' do cause 'Foo' end Non-Apple compilers don't have build numbers, so compiler failures are based on version strings instead. Internally non-Apple compilers can be distinguished because they are passed around as strings instead of symbols. In addition, this alters the priority list for compilers, with the following changes: * Apple GCC 4.2 and LLVM-GCC swap positions, with GCC now taking priority. (Maybe LLVM-GCC should just go away.) * Non-Apple GCC compilers are ranked below GCC 4.2 but above LLVM-GCC and Apple GCC 4.0.
2013-04-02Add new tests for fails_with DSLJack Nagel