-
-
Notifications
You must be signed in to change notification settings - Fork 347
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
WIP: perf(.travis.yml): merge travis builds to fall under 5 builds #2782
Conversation
Ok, my bad
|
I would personnally merge mvn339-jdk8 and jkd8 to keep only one. And I'd remove jdk9 since it won't be a LTS: we should only test against JDK8 and 11, since 11 is the new LTS. For corner cases we should have checks for 7, 9 and 10 on another CI. |
Sounds good to me. Following your advice, I've replaced As we are still one build short, I've left the merge between |
…avis-build-reduction
…avis-build-reduction
…avis-build-reduction
…avis-build-reduction
…avis-build-reduction
LGTM |
Waiting for #2789 to be merged before rebasing. |
…ges (#2789) Related to adding a travis build with jdk 11 See #2782 `CtFieldWrite.getTarget()` on `array.length` used to return a `CtVariableWrite` for some reasons... But with jdk 11 now returns a `CtVariableRead`... `FieldAccessTest#testFieldAccessOnUnknownType()` has been changed to handle both... by expecting a `CtVariableAccess`. This (combined with #2787) fixes tests for jdk 11 as can be seen here ( https://travis-ci.org/INRIA/spoon/jobs/460289160 ). Wether this is satisfaying or not, is up to debate. WDYT?
OK, this finally works. |
cleaning under the carpet of #2782
As travis builds are limited to 5 parallel builds for Spoon, I propose to merge the 3 fastest builds into one. (This 3 builds are just verification that are not tests, and are quite fast.)
Hopefully this new build is still faster than the slowest one, so it should be a net gain onboth time andresources.