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

0.9.0-fb1 fails to run on Travis-CI #714

Closed
kassens opened this issue Feb 17, 2016 · 4 comments
Closed

0.9.0-fb1 fails to run on Travis-CI #714

kassens opened this issue Feb 17, 2016 · 4 comments

Comments

@kassens
Copy link

kassens commented Feb 17, 2016

I updated a simple project from 0.8.2 to 0.9.0-fb1 (facebook/react-devtools#326) and found that jest no longer successfully runs on Travis-CI. Since the setup there seems pretty standard this seems like something worth fixing in jest directly.

The cause seems to be that the file system watcher watches too many files (relevant stack overflow answer).

Maybe the file watching could be turned off if process.env.TRAVIS is true. It's set by default?

@cpojer
Copy link
Member

cpojer commented Feb 18, 2016

I guess it makes sense to disable watchman on travis. Can you test whether calling Jest with --no-watchman solves this issue? If yes, I can add this to jest.

kassens added a commit to kassens/react-devtools that referenced this issue Feb 18, 2016
This might fix running jest 0.9.0 on Travis until jestjs/jest#714 is resolved.
@quantizor
Copy link
Contributor

Why is it watching files at all on a normal run?

@cpojer
Copy link
Member

cpojer commented Feb 19, 2016

I'm gonna close this, let's try 0.9.0-fb2 and reopen if it is still a problem.

@cpojer cpojer closed this as completed Feb 19, 2016
ghost pushed a commit that referenced this issue Feb 19, 2016
Summary:Fixes #714, probably also #722 and also facebook/react-native#6019
Closes #724

Differential Revision: D2953708

fb-gh-sync-id: 110a30d6c11256644c8e4f7ab1d7b7cb5fa1b021
shipit-source-id: 110a30d6c11256644c8e4f7ab1d7b7cb5fa1b021
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants