Skip to content
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

just to see that tests fail in master without any changes #749

Closed
wants to merge 1 commit into from

Conversation

eGavr
Copy link

@eGavr eGavr commented Jul 14, 2018

No description provided.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 96.208% when pulling e9a9aa5 on eGavr:tst into 8cd5f7a on paulmillr:master.

1 similar comment
@coveralls
Copy link

coveralls commented Jul 14, 2018

Coverage Status

Coverage remained the same at 96.208% when pulling e9a9aa5 on eGavr:tst into 8cd5f7a on paulmillr:master.

@srguiwiz
Copy link
Contributor

srguiwiz commented Jul 16, 2018

Just a clarification for the team, this demo PR not to be merged.

Just reminder you can run on your own machine

npm run test

and get familiar with what tests pass and fail.

Of course you would first need to have installed packages with

npm install

You may have known these steps, and have intended to demonstrate output of a test run.

The output of a test run, however, already is available in the previous commit before yours, behind the red X at https://github.com/paulmillr/chokidar/commits/master under Travis CI ☺

@eGavr
Copy link
Author

eGavr commented Jul 16, 2018

On my local machine I receive different results from time to time :)

All in all in travis this results are sometime different too

@paulmillr paulmillr closed this Sep 6, 2018
@paulmillr
Copy link
Owner

Almost fixed in master.

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.

None yet

4 participants