-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Karma 1.6 first-matcher (file-list fix) update is hard to debug #2675
Labels
Comments
steveworkman
changed the title
Karma 1.6 first-matcher update is hard to debug
Karma 1.6 first-matcher (file-list fix) update is hard to debug
Apr 24, 2017
I have the same issue. This might be related to the changes in #2620. My attempts to install the package from the repo, with the commits before this one, fail due to |
clintonb
pushed a commit
to openedx-unsupported/ecommerce
that referenced
this issue
May 3, 2017
In addition to updating the dependencies, I have removed the usage of semver modifiers. This is the second time (that I recall) these floating dependencies have been the source of broken tests on Travis, but not locally. In this case karma 1.6.0 is broken due to the issue described at karma-runner/karma#2675.
clintonb
pushed a commit
to openedx-unsupported/ecommerce
that referenced
this issue
May 3, 2017
In addition to updating the dependencies, I have removed the usage of semver modifiers. This is the second time (that I recall) these floating dependencies have been the source of broken tests on Travis, but not locally. In this case karma 1.6.0 is broken due to the issue described at karma-runner/karma#2675.
clintonb
pushed a commit
to openedx-unsupported/ecommerce
that referenced
this issue
May 3, 2017
In addition to updating the dependencies, I have removed the usage of semver modifiers. This is the second time (that I recall) these floating dependencies have been the source of broken tests on Travis, but not locally. In this case karma 1.6.0 is broken due to the issue described at karma-runner/karma#2675.
@clintonb @steveworkman could you create repository or gist which reproduce the problem? Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
Matchers in the matchers list bring back files according to their pattern. When the file is the first one in the list, it should be brough back.
Actual behaviour
Since 1.6 with this change for file-list some of my files aren't returned
Environment Details
OS X 10.11, PhantomJS browser
karma --version
): 1.6karma.config.js
fileV1.5 (working)
// list of files / patterns to load in the browser
Output:
v1.6 (not working)
Output:
Part of the problem here is that I have no idea how to find out what matcher is matching this. It would be really helpful if the warning could list out the matchers that it was matched for so that I can re-order it or change those matchers.
Steps to reproduce the behaviour
The text was updated successfully, but these errors were encountered: