Giter VIP home page Giter VIP logo

Comments (7)

eerolinna avatar eerolinna commented on July 30, 2024

The reason why it failed in travis can be seen in the error message here: https://travis-ci.org/MansMeg/posteriordb/jobs/601185982

Trim Trailing Whitespace.................................................Failed

hookid: trailing-whitespace

Files were modified by this hook. Additional output:

Fixing rpackage/tests/testthat/test-content.R

I created a PR #58 that strips this trailing whitespace and re-enables python3.7 job (this is the job that performs general linting like checking for trailing whitespace)

from posteriordb.

eerolinna avatar eerolinna commented on July 30, 2024

You can install pre-commit hooks that help notice trailing whitespace before committing (or you can choose to run the hooks also only before git push if you prefer). The instructions are here https://github.com/MansMeg/posteriordb/blob/master/CONTRIBUTING.md

If you don't want to run the checks automatically you can also replicate what the CI does by locally running

pre-commit run --all-files

This will automatically fix trailing whitespace issues, you'll only have to commit the changes afterwards (this is what Files were modified by this hook means in the error message)

from posteriordb.

eerolinna avatar eerolinna commented on July 30, 2024

You can also have RStudio remove trailing whitespace automatically when saving, see https://support.rstudio.com/hc/en-us/articles/200549016-Customizing-RStudio?mobile_site=true and "Strip trailing horizontal whitespace when saving"

You might also want to enable "Ensure that source files end with a new line" as CI checks for that as well.

from posteriordb.

MansMeg avatar MansMeg commented on July 30, 2024

Ah alright, so it is actually a problem with the R code?

from posteriordb.

MansMeg avatar MansMeg commented on July 30, 2024

Now fixed in 25d94d3

from posteriordb.

eerolinna avatar eerolinna commented on July 30, 2024

Yeah in this case the error was with general checks that apply to all files. There are also python-specific tests in the same job. I'll see if I can make a separate job for the general linting-like checks so it will be easier to pinpoint where the failure comes from

from posteriordb.

eerolinna avatar eerolinna commented on July 30, 2024

PR #60 separates the generic checks from python package tests

from posteriordb.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.