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

Apply fixes for Resing test as stated in #2421 #2422

Merged
merged 13 commits into from Dec 27, 2016

Conversation

Projects
None yet
3 participants
@jaguililla
Contributor

jaguililla commented Dec 27, 2016

No description provided.

@nbrady-techempower

This comment has been minimized.

Show comment
Hide comment
@nbrady-techempower

nbrady-techempower Dec 27, 2016

Member

Hi @jaguililla! I closed my PR in favor of yours here since it does the same thing, however this only fixes the default test. The resin test is still failing.

Member

nbrady-techempower commented Dec 27, 2016

Hi @jaguililla! I closed my PR in favor of yours here since it does the same thing, however this only fixes the default test. The resin test is still failing.

@LadyMozzarella

This comment has been minimized.

Show comment
Hide comment
@LadyMozzarella

LadyMozzarella Dec 27, 2016

Member

Merging this to fix the default test. Note that the resin implementation is still failing and will need some attention.

Member

LadyMozzarella commented Dec 27, 2016

Merging this to fix the default test. Note that the resin implementation is still failing and will need some attention.

@LadyMozzarella LadyMozzarella merged commit 104a391 into TechEmpower:master Dec 27, 2016

1 check failed

continuous-integration/travis-ci/pr The Travis CI build failed
Details
@jaguililla

This comment has been minimized.

Show comment
Hide comment
@jaguililla

jaguililla Dec 27, 2016

Contributor

I made everything just as Tapestry (only one test, add write permission to project files, deploy the war with 'hexagon.war' instead 'ROOT.war') and it did not work.

The Resin logs looks good also.

I also downloaded the WAR from the Vagrant development machine and run it in a local Resin and it worked.

Could it be because it is in the Kotlin folder instead the Java folder?

I need some help here, I'm not able to see the problem.

Contributor

jaguililla commented Dec 27, 2016

I made everything just as Tapestry (only one test, add write permission to project files, deploy the war with 'hexagon.war' instead 'ROOT.war') and it did not work.

The Resin logs looks good also.

I also downloaded the WAR from the Vagrant development machine and run it in a local Resin and it worked.

Could it be because it is in the Kotlin folder instead the Java folder?

I need some help here, I'm not able to see the problem.

@nbrady-techempower

This comment has been minimized.

Show comment
Hide comment
@nbrady-techempower

nbrady-techempower Dec 27, 2016

Member

@jaguililla Could you open an issue for the problems you're having? For starters, are you trying to hit port 9090? The benchmark_config for the resin test is 8080. If you don't come up with anything, we can carry on in an issue.

Member

nbrady-techempower commented Dec 27, 2016

@jaguililla Could you open an issue for the problems you're having? For starters, are you trying to hit port 9090? The benchmark_config for the resin test is 8080. If you don't come up with anything, we can carry on in an issue.

@jaguililla

This comment has been minimized.

Show comment
Hide comment
@jaguililla

jaguililla Dec 27, 2016

Contributor

I filed the #2434 issue. Thank you for your support!

Contributor

jaguililla commented Dec 27, 2016

I filed the #2434 issue. Thank you for your support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment