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

Jasmine bdd very slow because it is searching too many files #282

Closed
brooklynphotos opened this issue Aug 12, 2015 · 4 comments
Closed

Jasmine bdd very slow because it is searching too many files #282

brooklynphotos opened this issue Aug 12, 2015 · 4 comments
Labels
stale Issues with no activity

Comments

@brooklynphotos
Copy link

Loading the jetty server did not take more than a few seconds. Then pointing browser to a specific file, like /src/test/index.html took no time. But then if I wanted to try the root or /src, it took more than 6 MINUTES for the browser to get anything back. After a lot of testing, I realized that in the slow case, jasmine plugin is looking through all the directories in the directory where I am running mvn jasmine:bdd. That includes huge extjs directory, the build directory created by sencha cmd, which altogether contain tens of thousands of little text files. Is there a way to tell mvn jasmine:bdd to not look at everything? It seems the sourceIncludes or jsSrcDir merely tells the program to gather the names of source files in these directories; but it doesn't mean the program won't look at all the directories. Is that true? If so, is there a way for the program to look at specific places and not, say, the extjs library directory?

@mielw
Copy link

mielw commented Nov 9, 2016

Did you manage to solve (or work around) the problem? I got the same issue with my Ext Js test setup.

@blueberryfan
Copy link

blueberryfan commented Nov 21, 2017

I seem to have the same problem, but with the node_modules directory (where npm installs packages). If I delete the node_modules directory, my tests run in a couple of seconds, but with the directory there it takes more than a minute. Sometimes it times out. Seems like scanning the thousands of files in node_modules causes a problem.
How can I make the plugin completely ignore the npm node_modules directory?

I've tried to configure excludes like so, but none of them seem to make any difference. Am I missing something?

<configuration>
    <sourceExcludes>
            <exclude>**/node_modules/**/*.*</exclude>

            <exclude>myproj/subdirWithNodeStuff</exclude>
            <sourceExclude>myproj/subdirWithNodeStuff</sourceExclude>

            <exclude>myproj/subdirWithNodeStuff/**/*</exclude>
            <sourceExclude>myproj/subdirWithNodeStuff/**/*</sourceExclude>

            <exclude>myproj/subdirWithNodeStuff/node_modules</exclude>
            <sourceExclude>myproj/subdirWithNodeStuff/node_modules</sourceExclude>
    </sourceExcludes>
</configuration>

@github-actions
Copy link

github-actions bot commented Feb 4, 2021

This issue has been marked as stale because it has not been updated in 60 days. Please add a comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale Issues with no activity label Feb 4, 2021
@github-actions
Copy link

This issue was closed because it has been stalled for 7 days with no updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Issues with no activity
Projects
None yet
Development

No branches or pull requests

3 participants