Skip to content

Restricting when the umbrella cover runs#2512

Merged
dhermes merged 2 commits intogoogleapis:masterfrom
dhermes:move-cover
Oct 6, 2016
Merged

Restricting when the umbrella cover runs#2512
dhermes merged 2 commits intogoogleapis:masterfrom
dhermes:move-cover

Conversation

@dhermes
Copy link
Copy Markdown
Contributor

@dhermes dhermes commented Oct 6, 2016

First, swapping the cover envs. in the umbrella tox config:

isolated-cover --> cover
         cover --> umbrella-cover

and dropping the (now redunant) tox -e cover from .travis.yml. Finally, wrapping the after_success: Travis call to tox -e coveralls in a check to make sure it only runs on push builds (to speed up PR builds).

NOTE: This means that Coveralls will no longer be a check on PRs.

isolated-cover --> cover
         cover --> umbrella-cover

Also dropping `tox -e cover` from `.travis.yml` since it is
no redundant.
@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Oct 6, 2016
@daspecster
Copy link
Copy Markdown
Contributor

This looks good to me pending travis.

@dhermes
Copy link
Copy Markdown
Contributor Author

dhermes commented Oct 6, 2016

Unfortunately the build still took 8 minutes because just installing the lint environment took 80s (namespace packages!) and similarly the do-nothing system test envs took 45s and 70s. Finally the docs build took 200s.

Will try to get these down. I know Sphinx has support for incremental builds to it's worth taking a look. (I also know that tox disables Sphinx caching so we'd want a special hack there.)

@dhermes dhermes merged commit 4a299fe into googleapis:master Oct 6, 2016
@dhermes dhermes deleted the move-cover branch October 6, 2016 23:16
richkadel pushed a commit to richkadel/google-cloud-python that referenced this pull request May 6, 2017
Restricting when the umbrella cover runs
chalmerlowe pushed a commit that referenced this pull request Apr 1, 2026
PR created by the Librarian CLI to initialize a release. Merging this PR
will auto trigger a release.

Librarian Version: v0.7.0
Language Image:
us-central1-docker.pkg.dev/cloud-sdk-librarian-prod/images-prod/python-librarian-generator@sha256:160860d189ff1c2f7515638478823712fa5b243e27ccc33a2728669fa1e2ed0c
<details><summary>bigframes: 2.39.0</summary>

##
[2.39.0](googleapis/python-bigquery-dataframes@v2.38.0...v2.39.0)
(2026-03-31)

### Features

* add `df.bigquery.ai.forecast` method to pandas dataframe accessor
(#2518)
([1126cec9](googleapis/python-bigquery-dataframes@1126cec9))

* support full round-trip persistence for multimodal reference cols
(#2511)
([494a0a11](googleapis/python-bigquery-dataframes@494a0a11))

* expose DataFrame.bigquery in both pandas and bigframes DataFrames
(#2533)
([69fe3176](googleapis/python-bigquery-dataframes@69fe3176))

### Bug Fixes

* to_gbq may swap data columns when replace table (#2532)
([17ecc65e](googleapis/python-bigquery-dataframes@17ecc65e))

* handle aggregate operations on empty selections (#2510)
([34fb5daa](googleapis/python-bigquery-dataframes@34fb5daa))

* Localize BigQuery log suppression for gbq.py (#2541)
([af49ca29](googleapis/python-bigquery-dataframes@af49ca29))

* Respect remote function config changes even if logic unchanged (#2512)
([b9524284](googleapis/python-bigquery-dataframes@b9524284))

* support melting empty DataFrames without crashing (#2509)
([e8c4603](googleapis/python-bigquery-dataframes@e8c46032))

### Performance Improvements

* Make executor data uploads async internally (#2529)
([96597f0b](googleapis/python-bigquery-dataframes@96597f0b))

### Documentation

* gemini retouch of the index page for seo (#2514)
([2e5311e2](googleapis/python-bigquery-dataframes@2e5311e2))

* Rename Blob column references to ObjectRef column (#2535)
([44e0ffd9](googleapis/python-bigquery-dataframes@44e0ffd9))

</details>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla: yes This human has signed the Contributor License Agreement. testing

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants