-
Notifications
You must be signed in to change notification settings - Fork 824
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
Move to travis trusty dist #7092
Conversation
Oh cool :D |
It looked like behat had problems too - lets see if it works on master |
Oh no, pear again. =( |
Selenium doesn't seem to be working either :/ |
pear install seems fine |
If you push to the open-sourcerer fork, you'll get artifacts upload to aws. Then you can download selenium.log. |
Ok, I've re-enabled travis and added you with write permissions to https://github.com/open-sausages/silverstripe-framework |
gah - I'm not sure I have the motivation to look into this. the speed improvements on trusty look variable at best... I think I'll have more luck trying to get selenium running on a local trusty vm first |
I've found that there are some additional behat breakages caused by a recent release of php-webdriver module. Fix is at instaclick/php-webdriver#79 |
b8dbb60
to
a2f6706
Compare
still no luck |
Errors remind me why I stopped using pear. Try composer-install instead? |
a2f6706
to
309757b
Compare
the behat tests not running are really the big issue here, but I've pushed an attempted fix to use composer to install codesniffer |
1797d33
to
3dfbcd6
Compare
I've tried to get selenium running on a local trust vm and can't - so I'm going to bail at this point. If anyone has any ideas of how to fix this on travis, then please take a look, otherwise I'll close this. |
@chillu do you have any interest in investigating the selenium issues? |
3dfbcd6
to
c6858ae
Compare
composer.json
Outdated
@@ -94,8 +95,8 @@ | |||
"thirdparty/" | |||
], | |||
"scripts": { | |||
"lint": "phpcs src/ tests/php", | |||
"lint-clean": "phpcbf src/ tests/php", | |||
"lint": "vendor/bin/phpcs src/ tests/php", |
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 isn't going to work if framework isn't root, meaning these scripts are no longer useful to devs. Can you set the $PATH alias to vendor/bin instead in .travis.yml
?
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.
Sure
b02374a
to
118dd37
Compare
ce3178c
to
ba1a354
Compare
Selenium is falling apart on our build, so I'm triaging and milestoning this for 4.0 stable. I've also raised sveneisenschmidt/selenium-server-standalone#30 |
Looks like we need to install geckodriver to get support for firefox... I'll try to set this up before I dismiss the possibility immediately. :) |
Latest ESR is 52 of firefox.... we may need to lock our expected browser requirements to that (currently it's requesting v 9!)
|
OK - I've rerun the suite and it's still failing - I'm just at the point where I'm not really sure how to proceed... @tractorcow do you want to take it on from here? |
Yep I'm still working on it... there is quite a bit left to do (E.g. setup geckdriver, mink configuration upgrades) |
It looks like this could be the cause of recent failures on travis precise dist:
|
what a pain :/ |
New issue, https://github.com/instaclick/php-webdriver doesn't work with selenium 3. |
My next step would be to fork MinkSelenium2Driver module and update support for selenium3. Not going to do that now though; Maybe next hackday? |
I've setup a fork for working: {
"name": "silverstripe/installer",
"type": "silverstripe-recipe",
"description": "The SilverStripe Framework Installer",
"require": {
"php": ">=5.6.0",
"silverstripe/recipe-plugin": ">=0.1@dev <1.0",
"silverstripe/recipe-cms": "1.0.x-dev",
"silverstripe-themes/simple": "~3.2.0",
"silverstripe/serve": "dev-master",
"se/selenium-server-standalone": "3.5.3",
"behat/mink-selenium2-driver": "2.0.x-dev",
"silverstripe/behat-extension": "3.1.x-dev"
},
"repositories": [
{
"type": "vcs",
"url": "[email protected]:open-sausages/MinkSelenium2Driver.git"
},
{
"type": "vcs",
"url": "[email protected]:open-sausages/silverstripe-behat-extension.git"
}
]
} |
Just getting my head around this - here's the chain of events as far as I can tell:
@tractorcow The above is an updated version compared to what I posted on Slack. |
It looks like some of the issues I noticed upgrading to selenium3 were my own fault; Regarding php-webdriver/php-webdriver#468, you should only need to set |
I have most framework tests passing, but a few iframe switching bugs. Working branches: |
Also followed minkphp/Mink#158; The lack of this core API means having to upgrade various behat contexts to support facebook/webdriver directly (and undesirably). |
See silverstripe/silverstripe-framework#7092 for context. Trying out how this will go down on Behat tests in 3.x without further changes.
See silverstripe#7092 for context.
See silverstripe#7092 for context.
Note that I've switched to trusty without any other changes on cms, with successful builds: https://travis-ci.org/silverstripe/silverstripe-cms/jobs/274442114 I've created PRs to do a straight-up switch to precise for framework - just to see what the actual problem is (that's not mentioned in this thread AFAICT): 3.x PR for framework: #7366 My theory is that we just need to pin the Firefox dependency to something that still supports Selenium 2. |
So those builds both fail with:
3.x: https://travis-ci.org/silverstripe/silverstripe-framework/jobs/274445959 Now I'm updating them with a pinned Firefox version (31.0, same as cms travis config) and see if that's any different. |
More bad news, looks like upgrading to facebook/php-webdriver is blocked by php-webdriver/php-webdriver#462. |
OK, both those builds have passed - so the only thing that was necessary to fix this (apart from switching to trusty in the first place) was pinning of the FIrefox version we already had on CMS. Selenium states that it's supporting the current Firefox ESR - which would be v52 at the moment. I haven't seen any notice about Selenium 2 being unsupported (nothing mentioned in the announcement). It'll become increasingly infeasible to stay on Selenium 2, but looks like we don't have an immediate problem there. There's a PoC with Behat/Mink in Chrome Headless, which is said to be 3x as fast as the equivalent through Selenium - so that's promising. And it would mean we skip Selenium entirely (no longer needing Java would be nice...). I'm happy to keep going on Selenium 2 for a while and hope that someone gets to a stable version of that PoC in the meantime :D |
Replaced with #7367 |
#7091 but on master