Skip to content

[2.7] bpo-30417: Disable 'cpu' resource on Travis (GH-1928)#1964

Merged
zware merged 1 commit into
python:2.7from
zware:backport-c53b13-2.7
Jun 6, 2017
Merged

[2.7] bpo-30417: Disable 'cpu' resource on Travis (GH-1928)#1964
zware merged 1 commit into
python:2.7from
zware:backport-c53b13-2.7

Conversation

@zware

@zware zware commented Jun 6, 2017

Copy link
Copy Markdown
Member

Also weakens the 'should this be run?' regex to allow all builds when .travis.yml changes.
(cherry picked from commit c53b13b)

…onGH-1928)

Also weakens the 'should this be run?' regex to allow all builds when .travis.yml changes..
(cherry picked from commit c53b13b)
@codecov

codecov Bot commented Jun 6, 2017

Copy link
Copy Markdown

Codecov Report

❗ No coverage uploaded for pull request base (2.7@e14af32). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@          Coverage Diff           @@
##             2.7    #1964   +/-   ##
======================================
  Coverage       ?   83.66%           
======================================
  Files          ?     1371           
  Lines          ?   347182           
  Branches       ?        0           
======================================
  Hits           ?   290481           
  Misses         ?    56701           
  Partials       ?        0

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e14af32...0abde6c. Read the comment docs.

@zware zware merged commit ddf8f14 into python:2.7 Jun 6, 2017
@zware zware deleted the backport-c53b13-2.7 branch June 6, 2017 01:03
@zware zware changed the title [2.7] bpo-30417: Disable 'cpu' and 'tzdata' resources on Travis (GH-1928) [2.7] bpo-30417: Disable 'cpu' resource on Travis (GH-1928) Jun 6, 2017
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.

2 participants