-
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 PHP Fat-Free Framework #1734
Conversation
All test faild. |
Ah, the folder names all got changed for round 11. Basically, I would suggest closing this pull request and opening a new one off of master. |
Alright. I've updated the branch. It should be able to merge now. |
hm. Is this CI check related to this Framework test? What's the problem? |
Localtest failed. Here is log. ( http://sprunge.us/SOQY ) |
05fbfd0
to
d5b976a
Compare
Well actually I have no idea why it's not working. It worked in Round 10 before. What was changed? |
@msmith-techempower Is there a readme we can point to that helps explain all the reasons why we don't like PRs with the source code for the entire framework included? @ikkez Some context: all other frameworks (besides the 5-10 that have yet been updated, incl. fatfree) do not put their entire framework source code directly in the TFB repo, that is downloaded by the setup.sh script. Is this something you could add to this PR? |
@hamiltont Not to my knowledge... but there isn't much of that anyway. |
not anymore ;-) |
@hamiltont really? As far as I can see others have included the source files as well, and fat-free is one of those with a relative small code base (~150kb, hand-picked for this tests). I can remove the changelog file to save additional 30kb if you want. I am currently more interested in getting the test-suite running instead of setup optimizations. I guess I'm lost with both tasks. |
My Vagrant box returns the following result with f3-factory@4c03423:
The Travis CI runner instead fails because of I haven't found a solution in the documentation or a similar problem in Google Groups. Do you have an idea how to fix this problem? Also I would like to reset our |
@Rayne I did that already and force-pushed it into the current master that is used in this pull-request. There should be no merge conflicts anymore. |
@ikkez You are right that there aren't merge conflicts, but our
|
it's rebased now. |
Awesome! |
Can I find the complete travis ci error logs somewhere? I'm looking for the full response of this test: https://travis-ci.org/F3Community/FrameworkBenchmarks/jobs/96214489#L1701 |
Fat-Free uses a strict error_reporting setting by default. Because Php yaf seems to be installed globally as a php module #1521 and randomly fails to load, our error handler is triggered and shouts things like this:
Because of this, your test verification randomly fails... sometimes. Of course we don't need yaf, and we could probably adjust the error reporting level to get around this, but I don't see that our framework should clean up install requirements or ignore errors from others participants. |
Hmm, I'm not convinced that @ssmith-techempower Could you pull this and test locally; at least this will output error logs that can be attached to the task to better understand the issue. |
Fat-Free scans for already occurred system errors on its initialization. We already have a similar issue here bcosca/fatfree#851 which reveals a server issue before F3 starts. A way to clear system errors is to use the |
@@ -43,6 +43,49 @@ | |||
"display_name": "fat-free", | |||
"notes": "", | |||
"versus": "php" | |||
}, | |||
"php5": { | |||
"setup_file": "setup", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be "setup_file": "setup_php5"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh yes, indeed. thanks.
I'm not quite sure what happened on Travis; it got into the I see the line |
hm, should I just try to drop the php5 test for now, to see if it works, or will it be out of comparison with other frameworks, which are not using php7 already? |
Hmm, according to the log, it seems that there is still this timeout issue. I'm not really sure what is going on here, but it's hanging up in Travis-CI. |
Seems that there is STILL a hang-up in Travis and I am not sure why. @ssmith-techempower Can you test all the |
It's timing out my local install as well. Gets to " |
Thanks - it's odd that of all the PHP tests, this is the only one hanging in this way. |
|
||
F3DIR="$TROOT/src" | ||
|
||
[[ ! -e "$F3DIR" ]] || rm -r "$F3DIR" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rm
command here needs the f
flag to force the rm
to happen without bringing up a prompt, which was hanging Travis and my local install due to prompting about write-protected files.
looks good here https://travis-ci.org/F3Community/FrameworkBenchmarks/jobs/116216563 |
Looks good on my local install, and I trust your Travis job means it would succeed for us. Merging in. |
update PHP Fat-Free Framework
fixed an issue found in the logs and updated to v3.5.0.