-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
Broken tests #43
Comments
Hi all I just temporarily reverted my changes locally and the tests still fail. Interestingly, I changed the composer versions of some dependencies, back to a previous version that should be supported, and the test still failed, but with a different output. Also, on my fork of the repo, the tests were running fine back when I submitted, but now seem to fail after I have composer updated. Could this be related to changes in one of the dependencies? Unfortunately I don't know what the previous versions I was using are. |
HI all I have just checked out the last commit prior to any of our changes, updates composer and ran the tests. There are the same failures appearing (See below).
My guess is that these failures are due to changes in a composer dependency. I can attempt to narrow it down, but it may take some time. @sebastianbergmann Maybe you could shed a little light? Thanks Rob |
Actually.... What I said isn't correct. For the tests to run, you need to create a file called After doing this locally, all tests run and pass. I remember getting stuck at this point while I was making my changes.
Thanks Rob |
Cannot reproduce this anymore. |
After finally (sorry!) merging the pull requests sent by @bryanagee, @MajorCaiger, @fatalcoder, and @vpx, there are now failing tests:
The text was updated successfully, but these errors were encountered: