-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
CI: unary operator expected error in log files #26547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI: unary operator expected error in log files #26547
Conversation
Was this causing any other issues or was our CI just not running DB tests on travis? |
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. |
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. |
Codecov Report
@@ 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
Continue to review full report at Codecov.
|
Codecov Report
@@ 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
Continue to review full report at Codecov.
|
it's the other way round. db tests running on Travis only. |
lgtm. pls verify that the message is coming on the right builds; merge when ready. |
checked. |
fix error in azure log