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

Probably requires Mojolicious::Plugin::MountPSGI 0.13 #1

Closed
eserte opened this issue Jun 4, 2018 · 1 comment
Closed

Probably requires Mojolicious::Plugin::MountPSGI 0.13 #1

eserte opened this issue Jun 4, 2018 · 1 comment

Comments

@eserte
Copy link

eserte commented Jun 4, 2018

The test suite fails on some of my smoker systems:

Can't locate object method "new" via package "Mojolicious::Plugin::MountPSGI::Proxy" at /usr/perl5.16.3t/lib/site_perl/5.16.3/Mojolicious/Plugin/MountPSGI.pm line 26.
# Tests were run but no plan was declared and done_testing() was not seen.
# Looks like your test exited with 255 just after 3.
t/test2_tools_http_ua_mojo.t ........... 
Dubious, test returned 255 (wstat 65280, 0xff00)
All 3 subtests passed 
Can't locate object method "new" via package "Mojolicious::Plugin::MountPSGI::Proxy" at /usr/perl5.16.3t/lib/site_perl/5.16.3/Mojolicious/Plugin/MountPSGI.pm line 26.
t/test2_tools_http_ua_mojo__httpbin.t .. 
Dubious, test returned 255 (wstat 65280, 0xff00)
No subtests run 

This seems to happen if Mojolicious::Plugin::MountPSGI < 0.13 is installed:

****************************************************************
Regression 'mod:Mojolicious::Plugin::MountPSGI'
****************************************************************
Name           	       Theta	      StdErr	 T-stat
[0='const']    	      0.0000	      0.0000	   0.00
[1='eq_0.08']  	      0.0000	      0.0000	   0.00
[2='eq_0.09']  	      0.0000	      0.0000	   0.00
[3='eq_0.12']  	      0.0000	      0.0000	   0.00
[4='eq_0.13']  	      1.0000	      0.0000	12363730600323128.00

R^2= 1.000, N= 48, K= 5
****************************************************************
@plicease
Copy link
Member

plicease commented Jun 4, 2018

I think this must be an incompatibility between mojo and the plugin because I am not using ...::Proxy directly, but that would be par for the course in mojo land. Thank you for the report, I am happy to bump the requirement to 0.13 if it just makes things work!

@plicease plicease closed this as completed Jun 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants