Skip to content

Conversation

@simonjayhawkins
Copy link
Member

fix error in azure log

ci/setup_env.sh: line 121: [: ==: unary operator expected 
@WillAyd
Copy link
Member

WillAyd commented May 28, 2019

Was this causing any other issues or was our CI just not running DB tests on travis?

@simonjayhawkins
Copy link
Member Author

causing a spurious message in the azure logs. it's probably no big deal. Travis didn't run, so will need to re-run to check this didn't break anything on the Travis front.

@simonjayhawkins
Copy link
Member Author

so it appears Travis is not run for draft PRs. marking this as ready for review, but's it not ready! need to check the Travis logs.

@simonjayhawkins simonjayhawkins marked this pull request as ready for review May 28, 2019 18:42
@simonjayhawkins simonjayhawkins changed the title CI: unary operator expected error in log files [DO NOT MERGE] CI: unary operator expected error in log files May 28, 2019
@simonjayhawkins simonjayhawkins added the CI Continuous Integration label May 28, 2019
@codecov
Copy link

codecov bot commented May 28, 2019

Codecov Report

Merging #26547 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@ Coverage Diff @@ ## master #26547 +/- ## ========================================== - Coverage 91.77% 91.76% -0.01%  ========================================== Files 174 174 Lines 50638 50638 ========================================== - Hits 46471 46468 -3  - Misses 4167 4170 +3
Flag Coverage Δ
#multiple 90.3% <ø> (ø) ⬆️
#single 41.69% <ø> (-0.07%) ⬇️
Impacted Files Coverage Δ
pandas/io/gbq.py 78.94% <0%> (-10.53%) ⬇️
pandas/core/frame.py 97% <0%> (-0.12%) ⬇️
pandas/util/testing.py 90.7% <0%> (+0.1%) ⬆️

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 998a0de...ce2b4d0. Read the comment docs.

@codecov
Copy link

codecov bot commented May 28, 2019

Codecov Report

Merging #26547 into master will decrease coverage by <.01%.
The diff coverage is n/a.

Impacted file tree graph

@@ Coverage Diff @@ ## master #26547 +/- ## ========================================== - Coverage 91.77% 91.76% -0.01%  ========================================== Files 174 174 Lines 50642 50642 ========================================== - Hits 46476 46471 -5  - Misses 4166 4171 +5
Flag Coverage Δ
#multiple 90.3% <ø> (ø) ⬆️
#single 41.67% <ø> (-0.11%) ⬇️
Impacted Files Coverage Δ
pandas/io/gbq.py 78.94% <0%> (-10.53%) ⬇️
pandas/core/frame.py 97% <0%> (-0.12%) ⬇️
pandas/util/testing.py 90.6% <0%> (-0.11%) ⬇️

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 7629a18...a7a0adf. Read the comment docs.

@simonjayhawkins
Copy link
Member Author

or was our CI just not running DB tests on travis?

it's the other way round. db tests running on Travis only.

@simonjayhawkins simonjayhawkins changed the title [DO NOT MERGE] CI: unary operator expected error in log files CI: unary operator expected error in log files May 28, 2019
@jreback jreback added this to the 0.25.0 milestone May 29, 2019
@jreback
Copy link
Contributor

jreback commented May 29, 2019

lgtm. pls verify that the message is coming on the right builds; merge when ready.

@simonjayhawkins
Copy link
Member Author

pls verify that the message is coming on the right builds

checked.

@simonjayhawkins simonjayhawkins merged commit 93a67db into pandas-dev:master May 29, 2019
@simonjayhawkins simonjayhawkins deleted the unary-operator-expected branch May 29, 2019 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous Integration

3 participants