Skip to content

CI: Add print skipped tests into azure step #26698

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

Merged
merged 7 commits into from
Jun 10, 2019
Merged

CI: Add print skipped tests into azure step #26698

merged 7 commits into from
Jun 10, 2019

Conversation

xcz011
Copy link
Contributor

@xcz011 xcz011 commented Jun 7, 2019

@codecov
Copy link

codecov bot commented Jun 7, 2019

Codecov Report

Merging #26698 into master will decrease coverage by 50.58%.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff             @@
##           master   #26698       +/-   ##
===========================================
- Coverage   91.78%    41.2%   -50.59%     
===========================================
  Files         174      179        +5     
  Lines       50703    50767       +64     
===========================================
- Hits        46538    20918    -25620     
- Misses       4165    29849    +25684
Flag Coverage Δ
#multiple ?
#single 41.2% <ø> (-0.7%) ⬇️
Impacted Files Coverage Δ
pandas/io/formats/latex.py 0% <0%> (-100%) ⬇️
pandas/io/sas/sas_constants.py 0% <0%> (-100%) ⬇️
pandas/core/groupby/categorical.py 0% <0%> (-100%) ⬇️
pandas/tseries/plotting.py 0% <0%> (-100%) ⬇️
pandas/tseries/converter.py 0% <0%> (-100%) ⬇️
pandas/io/formats/html.py 0% <0%> (-99.37%) ⬇️
pandas/io/sas/sas7bdat.py 0% <0%> (-91.16%) ⬇️
pandas/io/sas/sas_xport.py 0% <0%> (-90.1%) ⬇️
pandas/core/sparse/scipy_sparse.py 10.14% <0%> (-89.86%) ⬇️
pandas/core/tools/numeric.py 10.14% <0%> (-89.86%) ⬇️
... and 139 more

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 cf25c5c...68c39a1. Read the comment docs.

@codecov
Copy link

codecov bot commented Jun 7, 2019

Codecov Report

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

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #26698      +/-   ##
==========================================
- Coverage   91.88%   91.87%   -0.01%     
==========================================
  Files         174      174              
  Lines       50701    50701              
==========================================
- Hits        46588    46583       -5     
- Misses       4113     4118       +5
Flag Coverage Δ
#multiple 90.41% <ø> (ø) ⬆️
#single 41.91% <ø> (-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 649ad5c...e06ebb8. Read the comment docs.

@datapythonista
Copy link
Member

This is the checks job, only the validate_docstrings.py tests are run here, and no tests are skipped there.

This is trickier than what it looks I'd say, ideally, I think we should unify how the tests are called, and add the printing of the skipped tests there. So the output is consistent among builds.

Closing this PR, but feel free to open a new one with those changes.

@datapythonista datapythonista added CI Continuous Integration Testing pandas testing functions or related to the test suite labels Jun 7, 2019
@datapythonista
Copy link
Member

CC: @jorisvandenbossche

@jorisvandenbossche
Copy link
Member

@datapythonista It's not that this "simply" needs to be moved to a step in the posix.yml template? The tests are there always called with ci/run_tests.sh, so not that what should be unified.

@datapythonista
Copy link
Member

I think the best approach would be to have this in ci/run_tests.sh. The print skipped is already in the travis docs, and in azure we'd probably like to add it to posix but also windows.

I'm ok with moving the code in this PR to posix.yml for now, but ideally I think we should avoid repeating it in every CI system.

@jorisvandenbossche
Copy link
Member

Isn't it actually valuable that it is a separate step? That makes it simpler to look at it in the Azure interface (one of its advantages that you can split the log)

@jorisvandenbossche
Copy link
Member

It would maybe be nice to move the if checks (for single multiple tests) to a common script, but I don't see the problem with repeating calling out to that script in each CI. We also repeat the call to ci/run_tests.sh.

Anyway, I think this provides enough short term value (eg for checking if the clipboard tests ran or not) to add like this for now.

@datapythonista
Copy link
Member

Good point, then I'd simply have the if statement for the single/multi inside the script, and not in the CI config.

@xcz011 do you mind doing that?

The changes would be:

  • Check for which of the files exist (the if in your code) inside ci/print_skipped.py, so we can simply call the script in the CI config
  • Update .travis.yml to remove the if
  • Add your changes (without the if) to ci/azure/posix.yml and ci/azure/windows.yml

Reopening this, so you can keep working on the same branch if you want.

Thanks!

@datapythonista datapythonista reopened this Jun 7, 2019
@xcz011 xcz011 closed this Jun 8, 2019
@xcz011
Copy link
Contributor Author

xcz011 commented Jun 8, 2019

Good point, then I'd simply have the if statement for the single/multi inside the script, and not in the CI config.

@xcz011 do you mind doing that?

The changes would be:

  • Check for which of the files exist (the if in your code) inside ci/print_skipped.py, so we can simply call the script in the CI config
  • Update .travis.yml to remove the if
  • Add your changes (without the if) to ci/azure/posix.yml and ci/azure/windows.yml

Reopening this, so you can keep working on the same branch if you want.

Thanks!

Good point, then I'd simply have the if statement for the single/multi inside the script, and not in the CI config.

@xcz011 do you mind doing that?

The changes would be:

  • Check for which of the files exist (the if in your code) inside ci/print_skipped.py, so we can simply call the script in the CI config
  • Update .travis.yml to remove the if
  • Add your changes (without the if) to ci/azure/posix.yml and ci/azure/windows.yml

Reopening this, so you can keep working on the same branch if you want.

Thanks!

Sure, I will try to do it and may need some help

@xcz011 xcz011 reopened this Jun 8, 2019
Copy link
Member

@datapythonista datapythonista left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job, @xcz011, the skipped tests are correctly displayed in the CI. Just added a couple of minor comments.

@@ -90,3 +90,8 @@ jobs:
Write-Error "$($matches[1]) tests failed"
}
displayName: Check for test failures
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you have this in quotes as the rest of displayName properties in the fie? Looks like they are not needed, but better to have it consistent.

export PATH=$HOME/miniconda3/bin:$PATH
source activate pandas-dev
python ci/print_skipped.py
displayName: 'print skipped test'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you capitalize the p and use tests instead of test? so the display name is Print skipped tests

export PATH=$HOME/miniconda3/bin:$PATH
source activate pandas-dev
python ci/print_skipped.py
displayName: 'print skipped test'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same changes as in the other file

Copy link
Member

@datapythonista datapythonista left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @xcz011, great job here. @jorisvandenbossche merge when you're happy.

@jorisvandenbossche jorisvandenbossche changed the title Add print skiped into azure step CI: Add print skipped tests into azure step Jun 10, 2019
@jorisvandenbossche jorisvandenbossche added this to the 0.25.0 milestone Jun 10, 2019
@jorisvandenbossche jorisvandenbossche merged commit 959e799 into pandas-dev:master Jun 10, 2019
@jorisvandenbossche
Copy link
Member

@xcz011 thanks a lot!

@xcz011 xcz011 deleted the azure_print_skip_test branch June 10, 2019 23:09
@xcz011
Copy link
Contributor Author

xcz011 commented Jun 10, 2019

@xcz011 thanks a lot!

Thanks all the helps !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Testing pandas testing functions or related to the test suite
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI - Azure: print skipped tests
3 participants