| Age | Commit message (Collapse) | Author |
|---|
|
Also, flag those that we never want to be in a manpage.
|
|
`e.tap` calls the tap method which wants a block on
`FormulaUnavailableError` so the previous approach is :-1:.
|
|
Handle the case where a `FormulaUnavailableError` does not contain a tap
reference so fall back to `CoreTap` in this case.
|
|
This will be useful in debugging (and recovering from) the situation
where sometimes formulae can't be found when specifying multiple on the
command-line.
|
|
Always run `git clean -ffdx` on HOMEBREW_REPOSITORY. Also, ensure that
if we can't find a formula that's logged.
|
|
There's edge-cases which is breaking tap CI.
|
|
Otherwise weird things happen and formulae can't be found.
|
|
This is set by Jenkins to indicate a downstream bottle upload job needs
to use `brew bottle --keep-old`.
|
|
test-bot: cleanup all repositories.
|
|
The test bot currently only focuses on doing cleanup on the current tap
and the HOMEBREW_REPOSITORY. This should be extended to cover all
repositories as e.g. a syntax error in homebrew/core can break the CI
for all the other taps.
|
|
|
|
If there's formulae changes or the specified argument is a formula then
don't waste time running e.g. `brew tests`.
|
|
Also report Cask coverage.
|
|
This allows changed formulae in taps to be tested in the proper order.
See #738 for more details.
|
|
|
|
|
|
Flips HOMEBREW_RUBY_MACHO to HOMEBREW_NO_RUBY_MACHO.
|
|
|
|
|
|
|
|
Assume Ruby 2
|
|
|
|
- ignore Cask's files in `readall` (for now, there's an intentional
syntax error that will need fixed)
- run Cask's tests if they exist
- don't check Cask's files in coverage reports (for now)
|
|
This can just live in `brew.sh` and then it doesn’t need repeated in
all the other places.
|
|
|
|
This reverts commit 24f7e671317dfe22f1d8e10426db2e9074674bc9.
|
|
|
|
When running on Travis CI, both the Linux and macOS build will send a
coverage report, causing them to be merged by Coveralls. This results
in inferior coverage due to the early stage of the Linux-specific tests
and is probably not what we want. Make sure we only send a report for
macOS (assuming we stick with a single macOS build in `.travis.yml`).
|
|
`any?` is not the opposite of `empty?`. Besides the case that
`[false, nil].any?` will return false, `any?`(O(n)) has much worse
performance than `empty?`(O(1)).
|
|
Rather than nudge people to run `--strict` and then ignore some of the
results sometimes (e.g. GitHub repository notability) instead add a
dedicated `--new-formula` option that implies this is a one-time
advisory check.
|
|
|
|
|
|
|
|
|
|
|
|
Make sure to call `brew tests` only once with `--coverage` to avoid
expensive multiple runs and to prevent later runs from overwriting
previously sent results to Coveralls. (The previous setup overwrote the
results from a regular run with results from the `--generic` run.)
The `--no-compat` variant without any other options specified seemed to
be the most appropriate for a coverage report.
Closes #546.
Signed-off-by: Martin Afanasjew <martin@afanasjew.de>
|
|
|
|
|
|
|
|
|
|
|
|
* test-bot: start running generic tests.
Start running the test suite in the "generic" mode i.e. a base layer for
non-OS X platforms to be able to use to ensure we don't break the generic code
for the parts of the code we've got running.
Currently this just runs the integration tests as that's the only useful suite
that's entirely passing but eventually this will be changed to run the full test
suite in generic mode.
* test_integration_cmds: fix tests on Linux.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
