On 2018-06-29 09:29, Carsten Haitzler wrote:
On Fri, 29 Jun 2018 05:44:37 + jaquil...@eagleeyet.net said:
I will start working on this once I am back from my honeymoon on the
22nd as I am getting married tomorrow so hopefully I can find some
tags
on phab by then to work on with some
On Fri, 29 Jun 2018 05:44:37 + jaquil...@eagleeyet.net said:
> I will start working on this once I am back from my honeymoon on the
> 22nd as I am getting married tomorrow so hopefully I can find some tags
> on phab by then to work on with some guidance :)
oh congrats + good luck! don't
I will start working on this once I am back from my honeymoon on the
22nd as I am getting married tomorrow so hopefully I can find some tags
on phab by then to work on with some guidance :)
On 2018-06-29 05:40, Carsten Haitzler wrote:
On Fri, 29 Jun 2018 05:31:20 + jaquil...@eagleeyet.net
On Fri, 29 Jun 2018 05:31:20 + jaquil...@eagleeyet.net said:
> Can someone start tagging bugs that need unit tests or is that already
> done?
That is a good idea. From now on when I see a bug that seems it could do with a
unit test (i.e. it's readily unit-testable), I'll add some tag - TBD.
Can someone start tagging bugs that need unit tests or is that already
done?
On 2018-06-28 11:28, Carsten Haitzler wrote:
On Thu, 28 Jun 2018 05:25:42 + jaquil...@eagleeyet.net said:
Hi all,
I think writing unit tests would be good for someone like me whose new
to the code base if it
On Fri, Jun 29, 2018 at 4:38 AM, Mike Blumenkrantz <
michael.blumenkra...@gmail.com> wrote:
> I agree that app testers are good, but ideally unit tests should cover all
> the codepaths which can be triggered by an app. We can use tools like lcov
> to verify that the same codepaths are being taken
I agree that app testers are good, but ideally unit tests should cover all
the codepaths which can be triggered by an app. We can use tools like lcov
to verify that the same codepaths are being taken and ensure that identical
code is being run in tests as in apps.
Testing in a controlled
On Thu, 28 Jun 2018 05:25:42 + jaquil...@eagleeyet.net said:
> Hi all,
>
> I think writing unit tests would be good for someone like me whose new
> to the code base if it helps to catch issues. My question though is do
> we have a tags on phab where senior devs post tickets for tests that
Hi all,
I think writing unit tests would be good for someone like me whose new
to the code base if it helps to catch issues. My question though is do
we have a tags on phab where senior devs post tickets for tests that
someone like me can grab and start working on?
On 2018-06-28 04:36,
On Wed, 27 Jun 2018 13:14:39 -0400 Mike Blumenkrantz
said:
> I don't think we need to do testing in EFL, we do have unit test coverage
> for these functions and they pass. Given that this has never occurred in
> any other circumstance (and we have testing), this should be considered an
>
On Thu, 28 Jun 2018 11:07:36 +0900 Hermet Park said:
> Additional explanation for the second,
>
> Unit test, TC, and automation tool is good but not enough.
> We need human testers absolutely. They could test apps, detect errors and
> then report it.
> For the progressive sw, this must be a
Additional explanation for the second,
Unit test, TC, and automation tool is good but not enough.
We need human testers absolutely. They could test apps, detect errors and
then report it.
For the progressive sw, this must be a mandatory, not an optional process.
For version release(maybe in the
I don't think we need to do testing in EFL, we do have unit test coverage
for these functions and they pass. Given that this has never occurred in
any other circumstance (and we have testing), this should be considered an
application bug only; I've already filed a ticket for it.
On Wed, Jun 27,
Okay we need to do some testing and make sure changes to eina/ecore/eio
file ops are not the culprit, because if they are... Ephoto, Rage,
Terminology, EFM, many gadgets, etc... are all possible to do the same.
On Wed, Jun 27, 2018, 9:56 AM Xavi Artigas wrote:
> What? I have been working with
What? I have been working with it on my dev machine!
I hope my recent changes to bring it back to life didn't cause this...
Xavi
El lun., 25 jun. 2018 9:06 p. m., Mike Blumenkrantz <
michael.blumenkra...@gmail.com> escribió:
> Hi,
>
> Do not attempt to use Eflete.
>
> I was attempting to
EFLETE JUST REMOVED MY HOME FOLDER.
You can say "Told you so" now.
I was importing an edj file into a project in a folder off my home, it took
a while, then it kicked me to the login screen and after logging back in...
nada.
Xavi
On Tue, 26 Jun 2018 at 05:54, Hermet Park wrote:
> Thankfully,
On Tue, 26 Jun 2018 11:41:29 +0930
Simon Lees wrote:
>
> Last time I tried to use it, it wouldn't build against the current
> stable efl release so I gave up, which is a shame because when it was
> working well it was a really useful tool.
It did not build when I first packaged it, but did in
It seems like you have two main points here:
1) The review process for components should require the approval of
"maintainers", or people who are experts in a given area, and not just
anyone with commit access.
I agree with this idea. While it would certainly be nice if everyone could
review
Thankfully, Xavi Artigas fixed. Even though unstable but it's compilable on
devel branch now.
Actually, efl has been bad at compatibility so far.
After 1 year leaving, Enventor has totally collapsed which was stable
enough.
It's not about interface nor compilation but behaviors.
UIs is too
On 26/06/18 04:36, Mike Blumenkrantz wrote:
> Hi,
>
> Do not attempt to use Eflete.
>
> I was attempting to examine a related issue from phab today on my test
> machine and Eflete somehow managed to delete nearly EVERYTHING from my home
> directory. All my .directories, all my source trees,
Hi,
Do not attempt to use Eflete.
I was attempting to examine a related issue from phab today on my test
machine and Eflete somehow managed to delete nearly EVERYTHING from my home
directory. All my .directories, all my source trees, everything deleted.
Fortunately, this was only a testing
21 matches
Mail list logo
