Re: [E-devel] Mac server sponsorship
Hello. On 23.07.2018 18:31, Mike Blumenkrantz wrote: > Actually, if we were able to do Mac builds elsewhere then this would > greatly improve our CI build times. Mac builders on Travis are very highly > contested and so have even fewer resources available than Linux builders. > Even on my CI feature branch, Mac builds take 2x longer (10+ mins more) > than Linux builds. The problem is that you can not simply hook up some external osx server to Travis to speed it up. Its a completely different resource. The only way I could see it used for CI would be through Phabricator's harbourmaster. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Hello. On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote: > On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt > said: > >> Hello. >> >> On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote: >>> Hi Guys, >>> >>> I am willing to work on getting a CI setup on a mac machine going. >>> >>> I am willing to sponsor a server. I happened to find the following >>> >>> https://www.hostmyapple.com/macdedicated.html >>> >>> What do you guys think? >> >> You know that we already have CI testing on OSX via TravisCI? >> >> What would this do better than the current CI setup we have? >> >> https://travis-ci.org/Enlightenment/efl (look at the build job with an >> apple as logo) > > run apps and debug them interactively? you'd need vnc or some remote > display/access setup ...but that. :) it'd require people to not fight over the > same display... i.e. one person at a time... :) If we have one osx system for CI builds and another one for debugging problems on OSX I easily see how they could be very different in terms of OSX versions, libraries, homebrew installs, etc. Anyway, I do not want to shoot this down. As long as someone else will take care of it and handles things I just take it as a gift horse. :-) regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] ABI/API report for 1.21.0-alpha1
Hello. One of the big missing steps towards a 1.21 release is to make sure we are not breaking ABI or API from older releases. If you want to help with the release please spare an hour and look over the report from ABI Laboratory and help to identify if we have any breaks not related to our beta APIs. https://abi-laboratory.pro/index.php?view=objects_report&l=efl&v1=1.20.7&v2=1.21.0-alpha1 regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ABI/API report for 1.21.0-alpha1
Hi, Not sure I understand how this works... Any removed symbol not prefixed with "efl_" is an ABI break? Because there are quite a few of those... Xavi On Tue, 24 Jul 2018 at 10:46, Stefan Schmidt wrote: > Hello. > > One of the big missing steps towards a 1.21 release is to make sure we > are not breaking ABI or API from older releases. If you want to help > with the release please spare an hour and look over the report from ABI > Laboratory and help to identify if we have any breaks not related to our > beta APIs. > > > https://abi-laboratory.pro/index.php?view=objects_report&l=efl&v1=1.20.7&v2=1.21.0-alpha1 > > regards > Stefan Schmidt > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
On Tue, 24 Jul 2018 09:28:05 +0200 Stefan Schmidt said: > Hello. > > On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote: > > On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt > > said: > > > >> Hello. > >> > >> On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote: > >>> Hi Guys, > >>> > >>> I am willing to work on getting a CI setup on a mac machine going. > >>> > >>> I am willing to sponsor a server. I happened to find the following > >>> > >>> https://www.hostmyapple.com/macdedicated.html > >>> > >>> What do you guys think? > >> > >> You know that we already have CI testing on OSX via TravisCI? > >> > >> What would this do better than the current CI setup we have? > >> > >> https://travis-ci.org/Enlightenment/efl (look at the build job with an > >> apple as logo) > > > > run apps and debug them interactively? you'd need vnc or some remote > > display/access setup ...but that. :) it'd require people to not fight over > > the same display... i.e. one person at a time... :) > > If we have one osx system for CI builds and another one for debugging > problems on OSX I easily see how they could be very different in terms > of OSX versions, libraries, homebrew installs, etc. that's massively better than only a CI system and no way to interactively debug things like copy & paste (ask netstar - he has a mac box to do that now). this isn't perfection, but it never will be. :) it's better than nothing as right now the CI systems do not allow dbeugging like i described. just builds. right? > Anyway, I do not want to shoot this down. As long as someone else will > take care of it and handles things I just take it as a gift horse. :-) > > regards > Stefan Schmidt > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ABI/API report for 1.21.0-alpha1
Hello. On 24.07.2018 10:46, Stefan Schmidt wrote: > Hello. > > One of the big missing steps towards a 1.21 release is to make sure we > are not breaking ABI or API from older releases. If you want to help > with the release please spare an hour and look over the report from ABI > Laboratory and help to identify if we have any breaks not related to our > beta APIs. > > https://abi-laboratory.pro/index.php?view=objects_report&l=efl&v1=1.20.7&v2=1.21.0-alpha1 My personal review is below. I ignored all beta and EO APIs here. Added: Ecore_Common.h, libecore.so.1.21.0 ecore_init_ex ( int argc, char** argv ) ecore_shutdown_ex ( ) I think the names are not descriptive at all. What should the _ex stand for here? The API description speaks about propagating events on the main loop after init and callback setup. Removed: edje_object.eo.legacy.h, libedje.so.1.20.7 edje_object_color_class_description_get ( Edje_Object const* obj, char const* color_class ) It could be argued that it was part of the edje_onject, but it was exposed as legacy API none the less? I still can find an EAPI definition in edje_util.c for it. Would be great if someone could shed some light on this one. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
On 24.07.2018 11:19, Carsten Haitzler wrote: > On Tue, 24 Jul 2018 09:28:05 +0200 Stefan Schmidt > said: > >> Hello. >> >> On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote: >>> On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt >>> said: >>> Hello. On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote: > Hi Guys, > > I am willing to work on getting a CI setup on a mac machine going. > > I am willing to sponsor a server. I happened to find the following > > https://www.hostmyapple.com/macdedicated.html > > What do you guys think? You know that we already have CI testing on OSX via TravisCI? What would this do better than the current CI setup we have? https://travis-ci.org/Enlightenment/efl (look at the build job with an apple as logo) >>> >>> run apps and debug them interactively? you'd need vnc or some remote >>> display/access setup ...but that. :) it'd require people to not fight over >>> the same display... i.e. one person at a time... :) >> >> If we have one osx system for CI builds and another one for debugging >> problems on OSX I easily see how they could be very different in terms >> of OSX versions, libraries, homebrew installs, etc. > > that's massively better than only a CI system and no way to interactively > debug > things like copy & paste (ask netstar - he has a mac box to do that now). this > isn't perfection, but it never will be. :) it's better than nothing as right > now the CI systems do not allow dbeugging like i described. just builds. > right? Just builds. I don't expect a CI system to be a debugging system. To me these are two very different things to do. The TravisCI setup for OSX already proved itself very useful by finding build breaks on code committed into master. You fancy a full blown OSX system with remote VNC access for manually compiling and debugging. That is fair and could be nice to have. Just nothing on my list to work on. If you and Jonathan want to work on setting this all up, just go ahead. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ABI/API report for 1.21.0-alpha1
Hello. On 24.07.2018 10:54, Xavi Artigas wrote: > Hi, > > Not sure I understand how this works... Any removed symbol not prefixed > with "efl_" is an ABI break? No. We have many more API's which are behind the EO or BETA defines (Some drm and wayland stuff, eo, eolian, etc) There is no easy filter to get through the list. Some is knowledge archived over time and some is actually looking at the current code and figure things out. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ABI/API report for 1.21.0-alpha1
¡Hola, There are a few none "efl_" APIs that have been beta before. And they can be changed. Examples: "elm_widget" "evas_vg" (not beta from now on, but it has been before) What I see as a bug is the fact that ELM_CNP_EVENT_SELECTION_CHANGED was removed ? Greetings, bu5hm4n On 07/24/2018 10:54 AM, Xavi Artigas wrote: Hi, Not sure I understand how this works... Any removed symbol not prefixed with "efl_" is an ABI break? Because there are quite a few of those... Xavi On Tue, 24 Jul 2018 at 10:46, Stefan Schmidt wrote: Hello. One of the big missing steps towards a 1.21 release is to make sure we are not breaking ABI or API from older releases. If you want to help with the release please spare an hour and look over the report from ABI Laboratory and help to identify if we have any breaks not related to our beta APIs. https://abi-laboratory.pro/index.php?view=objects_report&l=efl&v1=1.20.7&v2=1.21.0-alpha1 regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Sure, it would have to go through harbormaster or similar and we would not be mailing the server to Travis for them to use. Any series of builds which requires a macos on Travis is subject to delay until a macos builder can be provided, meaning we may end up having to wait an undetermined amount of time for each new build if a lot of macos builders are in use. If we could eliminate that builder from our build matrix, it would help us from this angle. On Tue, Jul 24, 2018 at 3:22 AM Stefan Schmidt wrote: > Hello. > > On 23.07.2018 18:31, Mike Blumenkrantz wrote: > > Actually, if we were able to do Mac builds elsewhere then this would > > greatly improve our CI build times. Mac builders on Travis are very > highly > > contested and so have even fewer resources available than Linux builders. > > Even on my CI feature branch, Mac builds take 2x longer (10+ mins more) > > than Linux builds. > > The problem is that you can not simply hook up some external osx server > to Travis to speed it up. Its a completely different resource. The only > way I could see it used for CI would be through Phabricator's > harbourmaster. > > regards > Stefan Schmidt > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ABI/API report for 1.21.0-alpha1
Regarding the edje function: https://phab.enlightenment.org/D4403 It looks like the function prototype was just removed during this conversion and then never added back? On Tue, Jul 24, 2018 at 5:28 AM Stefan Schmidt wrote: > Hello. > > On 24.07.2018 10:46, Stefan Schmidt wrote: > > Hello. > > > > One of the big missing steps towards a 1.21 release is to make sure we > > are not breaking ABI or API from older releases. If you want to help > > with the release please spare an hour and look over the report from ABI > > Laboratory and help to identify if we have any breaks not related to our > > beta APIs. > > > > > https://abi-laboratory.pro/index.php?view=objects_report&l=efl&v1=1.20.7&v2=1.21.0-alpha1 > > My personal review is below. I ignored all beta and EO APIs here. > > Added: > Ecore_Common.h, libecore.so.1.21.0 > ecore_init_ex ( int argc, char** argv ) > ecore_shutdown_ex ( ) > > I think the names are not descriptive at all. What should the _ex stand > for here? The API description speaks about propagating events on the > main loop after init and callback setup. > > > Removed: > edje_object.eo.legacy.h, libedje.so.1.20.7 > edje_object_color_class_description_get ( Edje_Object const* obj, char > const* color_class ) > > It could be argued that it was part of the edje_onject, but it was > exposed as legacy API none the less? I still can find an EAPI definition > in edje_util.c for it. Would be great if someone could shed some light > on this one. > > regards > Stefan Schmidt > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
On Tue, 24 Jul 2018 11:41:29 +0200 Stefan Schmidt said: > > > On 24.07.2018 11:19, Carsten Haitzler wrote: > > On Tue, 24 Jul 2018 09:28:05 +0200 Stefan Schmidt > > said: > > > >> Hello. > >> > >> On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote: > >>> On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt > >>> said: > >>> > Hello. > > On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote: > > Hi Guys, > > > > I am willing to work on getting a CI setup on a mac machine going. > > > > I am willing to sponsor a server. I happened to find the following > > > > https://www.hostmyapple.com/macdedicated.html > > > > What do you guys think? > > You know that we already have CI testing on OSX via TravisCI? > > What would this do better than the current CI setup we have? > > https://travis-ci.org/Enlightenment/efl (look at the build job with an > apple as logo) > >>> > >>> run apps and debug them interactively? you'd need vnc or some remote > >>> display/access setup ...but that. :) it'd require people to not fight over > >>> the same display... i.e. one person at a time... :) > >> > >> If we have one osx system for CI builds and another one for debugging > >> problems on OSX I easily see how they could be very different in terms > >> of OSX versions, libraries, homebrew installs, etc. > > > > that's massively better than only a CI system and no way to interactively > > debug things like copy & paste (ask netstar - he has a mac box to do that > > now). this isn't perfection, but it never will be. :) it's better than > > nothing as right now the CI systems do not allow dbeugging like i > > described. just builds. right? > > Just builds. I don't expect a CI system to be a debugging system. To me > these are two very different things to do. The TravisCI setup for OSX > already proved itself very useful by finding build breaks on code > committed into master. > > You fancy a full blown OSX system with remote VNC access for manually > compiling and debugging. That is fair and could be nice to have. Just > nothing on my list to work on. If you and Jonathan want to work on > setting this all up, just go ahead. Indeed when eagleye mailed this, this was my first thought as it would need nothing more than: 1. some kind of vnc setup 2. some kind of ssh access with accounts 3. some kind of sudo-like access then at least when things really need some work, people can ssh in, use vnc and develop/test without having to buy a mac themselves. it sure as hell isn't as nice as a local machine, but ... it is a big step up from just CI/test suites. :) -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
I think an ideal place for me to help the project is on the mac side of things. I can only sponsor 1 server. On 2018-07-24 14:01, Mike Blumenkrantz wrote: Sure, it would have to go through harbormaster or similar and we would not be mailing the server to Travis for them to use. Any series of builds which requires a macos on Travis is subject to delay until a macos builder can be provided, meaning we may end up having to wait an undetermined amount of time for each new build if a lot of macos builders are in use. If we could eliminate that builder from our build matrix, it would help us from this angle. On Tue, Jul 24, 2018 at 3:22 AM Stefan Schmidt wrote: Hello. On 23.07.2018 18:31, Mike Blumenkrantz wrote: > Actually, if we were able to do Mac builds elsewhere then this would > greatly improve our CI build times. Mac builders on Travis are very highly > contested and so have even fewer resources available than Linux builders. > Even on my CI feature branch, Mac builds take 2x longer (10+ mins more) > than Linux builds. The problem is that you can not simply hook up some external osx server to Travis to speed it up. Its a completely different resource. The only way I could see it used for CI would be through Phabricator's harbourmaster. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Ssh is All that’s needed as far as I know. Sent from my iPhone > On 24 Jul 2018, at 16:14, Carsten Haitzler wrote: > > On Tue, 24 Jul 2018 11:41:29 +0200 Stefan Schmidt > said: > >> >> >>> On 24.07.2018 11:19, Carsten Haitzler wrote: >>> On Tue, 24 Jul 2018 09:28:05 +0200 Stefan Schmidt >>> said: >>> Hello. > On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote: > On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt > said: > >> Hello. >> >>> On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote: >>> Hi Guys, >>> >>> I am willing to work on getting a CI setup on a mac machine going. >>> >>> I am willing to sponsor a server. I happened to find the following >>> >>> https://www.hostmyapple.com/macdedicated.html >>> >>> What do you guys think? >> >> You know that we already have CI testing on OSX via TravisCI? >> >> What would this do better than the current CI setup we have? >> >> https://travis-ci.org/Enlightenment/efl (look at the build job with an >> apple as logo) > > run apps and debug them interactively? you'd need vnc or some remote > display/access setup ...but that. :) it'd require people to not fight over > the same display... i.e. one person at a time... :) If we have one osx system for CI builds and another one for debugging problems on OSX I easily see how they could be very different in terms of OSX versions, libraries, homebrew installs, etc. >>> >>> that's massively better than only a CI system and no way to interactively >>> debug things like copy & paste (ask netstar - he has a mac box to do that >>> now). this isn't perfection, but it never will be. :) it's better than >>> nothing as right now the CI systems do not allow dbeugging like i >>> described. just builds. right? >> >> Just builds. I don't expect a CI system to be a debugging system. To me >> these are two very different things to do. The TravisCI setup for OSX >> already proved itself very useful by finding build breaks on code >> committed into master. >> >> You fancy a full blown OSX system with remote VNC access for manually >> compiling and debugging. That is fair and could be nice to have. Just >> nothing on my list to work on. If you and Jonathan want to work on >> setting this all up, just go ahead. > > Indeed when eagleye mailed this, this was my first thought as it would need > nothing more than: > > 1. some kind of vnc setup > 2. some kind of ssh access with accounts > 3. some kind of sudo-like access > > then at least when things really need some work, people can ssh in, use vnc > and develop/test without having to buy a mac themselves. it sure as hell isn't > as nice as a local machine, but ... it is a big step up from just CI/test > suites. :) > > -- > - Codito, ergo sum - "I code, therefore I am" -- > Carsten Haitzler - ras...@rasterman.com > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Leave setup and administration to me. Is this a green light on this? On 2018-07-24 07:28, Stefan Schmidt wrote: Hello. On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote: On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt said: Hello. On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote: Hi Guys, I am willing to work on getting a CI setup on a mac machine going. I am willing to sponsor a server. I happened to find the following https://www.hostmyapple.com/macdedicated.html What do you guys think? You know that we already have CI testing on OSX via TravisCI? What would this do better than the current CI setup we have? https://travis-ci.org/Enlightenment/efl (look at the build job with an apple as logo) run apps and debug them interactively? you'd need vnc or some remote display/access setup ...but that. :) it'd require people to not fight over the same display... i.e. one person at a time... :) If we have one osx system for CI builds and another one for debugging problems on OSX I easily see how they could be very different in terms of OSX versions, libraries, homebrew installs, etc. Anyway, I do not want to shoot this down. As long as someone else will take care of it and handles things I just take it as a gift horse. :-) regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
I have no problem with setting it up with harbourmaster. Do you have any documentation on how to set it up or how to interact with HM? On 2018-07-24 07:21, Stefan Schmidt wrote: Hello. On 23.07.2018 18:31, Mike Blumenkrantz wrote: Actually, if we were able to do Mac builds elsewhere then this would greatly improve our CI build times. Mac builders on Travis are very highly contested and so have even fewer resources available than Linux builders. Even on my CI feature branch, Mac builds take 2x longer (10+ mins more) than Linux builds. The problem is that you can not simply hook up some external osx server to Travis to speed it up. Its a completely different resource. The only way I could see it used for CI would be through Phabricator's harbourmaster. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
On Tue, 24 Jul 2018 20:03:32 +0200 Jonathan Aquilina said: > Ssh is All that’s needed as far as I know. would need more than that for vnc... sure - set up ssh tunnels for vnc.. but it still is a another service to support... > Sent from my iPhone > > > On 24 Jul 2018, at 16:14, Carsten Haitzler wrote: > > > > On Tue, 24 Jul 2018 11:41:29 +0200 Stefan Schmidt > > said: > > > >> > >> > >>> On 24.07.2018 11:19, Carsten Haitzler wrote: > >>> On Tue, 24 Jul 2018 09:28:05 +0200 Stefan Schmidt > >>> said: > >>> > Hello. > > > On 23.07.2018 11:11, Carsten Haitzler (The Rasterman) wrote: > > On Mon, 23 Jul 2018 09:42:43 +0200 Stefan Schmidt > > said: > > > >> Hello. > >> > >>> On 23.07.2018 06:59, jaquil...@eagleeyet.net wrote: > >>> Hi Guys, > >>> > >>> I am willing to work on getting a CI setup on a mac machine going. > >>> > >>> I am willing to sponsor a server. I happened to find the following > >>> > >>> https://www.hostmyapple.com/macdedicated.html > >>> > >>> What do you guys think? > >> > >> You know that we already have CI testing on OSX via TravisCI? > >> > >> What would this do better than the current CI setup we have? > >> > >> https://travis-ci.org/Enlightenment/efl (look at the build job with an > >> apple as logo) > > > > run apps and debug them interactively? you'd need vnc or some remote > > display/access setup ...but that. :) it'd require people to not fight > > over the same display... i.e. one person at a time... :) > > If we have one osx system for CI builds and another one for debugging > problems on OSX I easily see how they could be very different in terms > of OSX versions, libraries, homebrew installs, etc. > >>> > >>> that's massively better than only a CI system and no way to interactively > >>> debug things like copy & paste (ask netstar - he has a mac box to do that > >>> now). this isn't perfection, but it never will be. :) it's better than > >>> nothing as right now the CI systems do not allow dbeugging like i > >>> described. just builds. right? > >> > >> Just builds. I don't expect a CI system to be a debugging system. To me > >> these are two very different things to do. The TravisCI setup for OSX > >> already proved itself very useful by finding build breaks on code > >> committed into master. > >> > >> You fancy a full blown OSX system with remote VNC access for manually > >> compiling and debugging. That is fair and could be nice to have. Just > >> nothing on my list to work on. If you and Jonathan want to work on > >> setting this all up, just go ahead. > > > > Indeed when eagleye mailed this, this was my first thought as it would need > > nothing more than: > > > > 1. some kind of vnc setup > > 2. some kind of ssh access with accounts > > 3. some kind of sudo-like access > > > > then at least when things really need some work, people can ssh in, use vnc > > and develop/test without having to buy a mac themselves. it sure as hell > > isn't as nice as a local machine, but ... it is a big step up from just > > CI/test suites. :) > > > > -- > > - Codito, ergo sum - "I code, therefore I am" -- > > Carsten Haitzler - ras...@rasterman.com > > > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Hello. On 24.07.2018 22:25, jaquil...@eagleeyet.net wrote: > I have no problem with setting it up with harbourmaster. > > Do you have any documentation on how to set it up or how to interact > with HM? Marcel has been looking into this. He should be able to help. Before we start anything like this though the system should be already installed with all the efl dependencies and a buld of efl should work over ssh. If you also want to use this server for debugging I would argue that you need two different user for the CI and the debugging jobs. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Hello. On 24.07.2018 22:18, jaquil...@eagleeyet.net wrote: > Leave setup and administration to me. > > Is this a green light on this? I never blocked it. From my side its fine if you want to do this. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Hello. On 24.07.2018 16:01, Mike Blumenkrantz wrote: > > Any series of builds which requires a macos on Travis is subject to delay > until a macos builder can be provided, meaning we may end up having to wait > an undetermined amount of time for each new build if a lot of macos > builders are in use. If we could eliminate that builder from our build > matrix, it would help us from this angle. Yes, the osx builds are a bottleneck. With both factors, delay until the job starts and build time itself. We have not made real use of harbourmaster and drydock yet, which means we will have to learn if that really is a good option for all this. We will also see if the hosted mac server really gives the speed increase in CI you hope for. Something to try out but with various unknowns and risks attached. Jonathan wanted to set this up. I would say we wait until he has somethign that can build efl over ssh and we can see how it would integrate with phab once that is done. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ABI/API report for 1.21.0-alpha1
Hello. On 24.07.2018 16:07, Mike Blumenkrantz wrote: > Regarding the edje function: > > https://phab.enlightenment.org/D4403 > > It looks like the function prototype was just removed during this > conversion and then never added back? Good point. Conrad, could you shed some light one what happened to edje_object_color_class_description_get ? We are looking into API breaks for the 1.21 release and wonder what happened with this function. regards Stefan Schmidt > On Tue, Jul 24, 2018 at 5:28 AM Stefan Schmidt > wrote: > >> Hello. >> >> On 24.07.2018 10:46, Stefan Schmidt wrote: >>> Hello. >>> >>> One of the big missing steps towards a 1.21 release is to make sure we >>> are not breaking ABI or API from older releases. If you want to help >>> with the release please spare an hour and look over the report from ABI >>> Laboratory and help to identify if we have any breaks not related to our >>> beta APIs. >>> >>> >> https://abi-laboratory.pro/index.php?view=objects_report&l=efl&v1=1.20.7&v2=1.21.0-alpha1 >> >> My personal review is below. I ignored all beta and EO APIs here. >> >> Added: >> Ecore_Common.h, libecore.so.1.21.0 >> ecore_init_ex ( int argc, char** argv ) >> ecore_shutdown_ex ( ) >> >> I think the names are not descriptive at all. What should the _ex stand >> for here? The API description speaks about propagating events on the >> main loop after init and callback setup. >> >> >> Removed: >> edje_object.eo.legacy.h, libedje.so.1.20.7 >> edje_object_color_class_description_get ( Edje_Object const* obj, char >> const* color_class ) >> >> It could be argued that it was part of the edje_onject, but it was >> exposed as legacy API none the less? I still can find an EAPI definition >> in edje_util.c for it. Would be great if someone could shed some light >> on this one. >> >> regards >> Stefan Schmidt >> >> >> -- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> enlightenment-devel mailing list >> enlightenment-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >> > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] ABI/API report for 1.21.0-alpha1
Hello. On 24.07.2018 11:21, Marcel Hollerbach wrote: > > What I see as a bug is the fact that ELM_CNP_EVENT_SELECTION_CHANGED was > removed ? Which commit did remove it? Does it mention any reason on it? Something we need to follow up on. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Seeing as there is quite a bit of interest in this tonight, which is going to probably be the first evening relaxed at home with my wife since we got back from the honeymoon, I will purchase the server. Can someone open up some tickets on Phabricator with what you guys want me to do and what the end goal is that way progress can be tracked by those following the ticket. If not I will open a ticket on my helpdesk. I’m also a bit concerned about accuracy of documentation. Is everything up to date? Sent from my iPhone > On 25 Jul 2018, at 08:26, Stefan Schmidt wrote: > > Hello. > >> On 24.07.2018 16:01, Mike Blumenkrantz wrote: >> >> Any series of builds which requires a macos on Travis is subject to delay >> until a macos builder can be provided, meaning we may end up having to wait >> an undetermined amount of time for each new build if a lot of macos >> builders are in use. If we could eliminate that builder from our build >> matrix, it would help us from this angle. > > Yes, the osx builds are a bottleneck. With both factors, delay until the > job starts and build time itself. > > We have not made real use of harbourmaster and drydock yet, which means > we will have to learn if that really is a good option for all this. We > will also see if the hosted mac server really gives the speed increase > in CI you hope for. Something to try out but with various unknowns and > risks attached. > > Jonathan wanted to set this up. I would say we wait until he has > somethign that can build efl over ssh and we can see how it would > integrate with phab once that is done. > > regards > Stefan Schmidt > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Hi Jonathan, Regarding accuracy of documentation... expect anything. I have found infrastructure docs to vary in quality, and to be generally pretty scattered. Since you will be setting everything up from scratch, this is an EXCELLENT opportunity to write down every step along the way and update any missing doc. That would be enormous. I can take care of that if you send me your notes, once you have everything up and running. Thanks! Xavi On Wed, 25 Jul 2018 at 08:41, Jonathan Aquilina wrote: > Seeing as there is quite a bit of interest in this tonight, which is going > to probably be the first evening relaxed at home with my wife since we got > back from the honeymoon, I will purchase the server. Can someone open up > some tickets on Phabricator with what you guys want me to do and what the > end goal is that way progress can be tracked by those following the > ticket. If not I will open a ticket on my helpdesk. > > I’m also a bit concerned about accuracy of documentation. Is everything up > to date? > > Sent from my iPhone > > > On 25 Jul 2018, at 08:26, Stefan Schmidt > wrote: > > > > Hello. > > > >> On 24.07.2018 16:01, Mike Blumenkrantz wrote: > >> > >> Any series of builds which requires a macos on Travis is subject to > delay > >> until a macos builder can be provided, meaning we may end up having to > wait > >> an undetermined amount of time for each new build if a lot of macos > >> builders are in use. If we could eliminate that builder from our build > >> matrix, it would help us from this angle. > > > > Yes, the osx builds are a bottleneck. With both factors, delay until the > > job starts and build time itself. > > > > We have not made real use of harbourmaster and drydock yet, which means > > we will have to learn if that really is a good option for all this. We > > will also see if the hosted mac server really gives the speed increase > > in CI you hope for. Something to try out but with various unknowns and > > risks attached. > > > > Jonathan wanted to set this up. I would say we wait until he has > > somethign that can build efl over ssh and we can see how it would > > integrate with phab once that is done. > > > > regards > > Stefan Schmidt > > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Mac server sponsorship
Hello. On 25.07.2018 08:41, Jonathan Aquilina wrote: > Seeing as there is quite a bit of interest in this tonight, which is going to > probably be the first evening relaxed at home with my wife since we got back > from the honeymoon, I will purchase the server. Can someone open up some > tickets on Phabricator with what you guys want me to do and what the end goal > is that way progress can be tracked by those following the ticket. If not I > will open a ticket on my helpdesk. > > I’m also a bit concerned about accuracy of documentation. Is everything up to > date? https://www.enlightenment.org/docs/distros/osx-start.md https://git.enlightenment.org/core/efl.git/tree/.ci/ci-osx-deps.sh https://git.enlightenment.org/core/efl.git/tree/.ci/ci-osx-build.sh This is what I used when setting up the osx builds on Travis. Likely there are more details to figure out. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
