-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Update framework version to 1.3.5 #1761
Update framework version to 1.3.5 #1761
Conversation
3 tests: fortune, db, query failed.
|
I would like to request some help here. When I run the tests from my fork (inside the vagrant-development VM) they pass, but they always fail in Travis. How could I replay the error in my local environment? |
We still have issues with Travis that need to be addressed - we will check this out and run it locally to test it before merging, rather than relying on Travis. |
Ok, thank you for the information! |
Retest this please |
Could you please send an update about the Travis problems? should I pick your latest master changes? |
* Make sinatra-sequel framework compatible with JRuby 9K * Add runner, language setup, and benchmark config for sinatra-sequel-puma-jruby * Bug Fix: sinatra-sequel framework was applying updates on /updates, but returning the original records (instead of the updated records) * Incorporated findings from StackProf analysis and clearer reading of Sequel documentation
Add sinatra-sequel-puma-jruby benchmark
Updated composer.json to pull Cygnite v1.3
Trying to fix Travis
@jamming We have just pushed a bunch of Travis-CI fixes into master; if you could rebase your branch from our master and push the changes, Travis-CI should be able to test automatically. |
Mmmm... My framework pass the tests but others don't, will it be merged? |
Yes, your tests pass: https://travis-ci.org/TechEmpower/FrameworkBenchmarks/jobs/96141934 LGTM! |
Update framework version to 1.3.5
No description provided.