On 10.01.2014 06:23, Paul Larson wrote:
as well as unity8 crash in default and in click-image-tests.
The two .crash files in click-image-tests were not pre-processed by
apport, any idea why? Hmm it seems they're corrupted - apport-cli fails
to process them.
The one in default is the usual:
On 09.01.2014 21:11, Dimitri John Ledkov wrote:
$ ./scripts/run-all.sh
Any reason for unity8 not being part of that?
--
Michał (Saviq) Sawicz
Canonical Services Ltd.
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launc
On Fri, Jan 10, 2014 at 6:23 AM, Paul Larson wrote:
> = Mako =
> 100% pass (no reruns for anything)
> But we saw several crashes - dialer-app (which has been going on for a
> while) as well as unity8 crash in default and in click-image-tests.
> Default tests also saw a crash in whoopsie:
> http://
On Thu, Jan 9, 2014 at 6:24 PM, Didier Roche wrote:
>
> notes_app (Bill):
> http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:
> 20140105:20131223.2/5882/notes-app-autopilot/638428/
This test fails very early on (in setUp), waiting for the toolbar to close.
I suspect the app wasn’t started prop
On Fri, Jan 10, 2014 at 10:19 AM, Olivier Tilloy
wrote:
> On Thu, Jan 9, 2014 at 6:24 PM, Didier Roche wrote:
>>
>> notes_app (Bill):
>>
>> http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/
>
>
> This test fails very early on (in setUp), waiti
On 10 January 2014 09:15, Alexander Sack wrote:
> On Fri, Jan 10, 2014 at 6:23 AM, Paul Larson
> wrote:
>> = Mako =
>> 100% pass (no reruns for anything)
>> But we saw several crashes - dialer-app (which has been going on for a
>> while) as well as unity8 crash in default and in click-image-test
== Mako ==
100% pass rate with no reruns.
3 Unity8 crashes (with gellery, webbrowser and ubuntuuitoolkit tests)
usual dialer app crash with dialer app test
== Maguro ==
ubuntu-ui-toolkit-autopilot: 1 failure ( r120 had no failures)
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/121:20140110
On Fri, Jan 10, 2014 at 10:19 AM, Olivier Tilloy <
olivier.til...@canonical.com> wrote:
> On Thu, Jan 9, 2014 at 6:24 PM, Didier Roche wrote:
>>
>> notes_app (Bill):
>> http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:
>> 20140105:20131223.2/5882/notes-app-autopilot/638428/
>
>
> This test fail
On Fri, Jan 10, 2014 at 10:46 AM, Alexander Sack wrote:
> On Fri, Jan 10, 2014 at 10:19 AM, Olivier Tilloy
> wrote:
> > On Thu, Jan 9, 2014 at 6:24 PM, Didier Roche
> wrote:
> >>
> >> notes_app (Bill):
> >>
> >>
> http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes
On 10 January 2014 09:00, Michał Sawicz wrote:
> On 09.01.2014 21:11, Dimitri John Ledkov wrote:
>>
>> $ ./scripts/run-all.sh
>
>
> Any reason for unity8 not being part of that?
I've now added unity8, but I believe log collaction is still affected.
Emulator dies before any artifacts / clientlogs/
On 10.01.2014 11:26, Para Siva wrote:
3 Unity8 crashes (with gellery, webbrowser and ubuntuuitoolkit tests)
Same as before:
terminate called after throwing an instance of
'boost::exception_detail::clone_impl
>'
what(): could not activate surface with eglMakeCurrent
One other did not retr
Evan Dandrea [2014-01-10 10:10 +]:
> The phone does not presently do a second-phase processing of crash
> files (adding package information, hooks, etc)
Not the one itself, but our CI test machinery is doing that. It calls
/usr/share/apport/whoopsie-upload-all after running the tests, which
d
On 10/01/14 02:23, Paul Larson wrote:
= Mako =
100% pass (no reruns for anything)
But we saw several crashes - dialer-app (which has been going on for a
while) as well as unity8 crash in default and in click-image-tests.
Default tests also saw a crash in whoopsie:
http://ci.ubuntu.com/smokeng/tr
Dear Developers,
This is Viswaprasath from India doing my final year at VEC,Chennai . I
recently came to know about Native development for Ubuntu touch apps.
Previously I have developed apps using HTML5 technologies. But I prefer to
develop with QML.
I feel we need to develop some examples applic
We do clean out /var/log/crashes both at the beginning before a test
as run, as well as after uploading crashes. I agree, it's very
unlikely that the crash itself has anything to do with running click
list --manifest, but it's not unheard of to see crashes that happen
not because of the test runnin
Hi Viswaprasath
I'd suggest to look at already made apps. The default ones for Ubuntu for
examples.
All Ubuntu code is hosted on launchpad.net. The core apps (the ones
installed as default on the phone) can be found here:
https://launchpad.net/ubuntu-phone-coreapps
There are also a lot of develop
Hi Viswaprasath,
As an example of a third party open-source app, I developed Tasks, which is
available at https://github.com/iBeliever/tasks-app. It is a moderately-sized
application, and includes U1db for storage and has a convergent UI that works
on the phone, desktop, and tablet.
Hope you f
Hello everybody,
we are currently preparing materials for the "App Dev School"
initiative, in which we will ask app developers to go out to their LUG,
LoCo, university class or some conference and show how simple it is to
write apps.
Michał Karnicki was kind enough to provide us with a simpl
Hello everyone
The unstable Ubuntu Touch image is now at its latest and finest with
image 121 which has just been promoted!
It contains:
* some new system-settings updates (as part of the continuing citrain
new CI developer experience)
* session migration user data support
* some theme chang
On 10 January 2014 17:27, Didier Roche wrote:
> Hello everyone
>
> The unstable Ubuntu Touch image is now at its latest and finest with image
> 121 which has just been promoted!
>
> It contains:
> * some new system-settings updates (as part of the continuing citrain new CI
> developer experience)
On Fri, Jan 10, 2014 at 10:10:14AM +, Evan Dandrea wrote:
> There's a deeper problem here. Didier informs me that they were seeing
> a lot of crashes in unity8 with a smashed stacktrace. They realised
> the dying unity process was getting reaped and restarted by upstart
> while still being proc
On Jan 09, 2014, at 08:34 AM, Didier Roche wrote:
>So, the idea that we enforced from this process are quite simple:
>source package name == project name. So, if you have "foo" source package in
>Ubuntu where we are upstream for, you know that you can confidently bzr
>branch lp:foo and that's wha
On 10.01.2014 20:04, Steve Langasek wrote:
I don't see how this analysis can be correct. upstart receives no signal
from the kernel that the process has died until after the core handler is
finished, and if the unity8 process has died with a segfault there's no
process for upstart to kill anyway
On Fri, Jan 10, 2014 at 11:24:52PM +0100, Michał Sawicz wrote:
> On 10.01.2014 20:04, Steve Langasek wrote:
> >I don't see how this analysis can be correct. upstart receives no signal
> >from the kernel that the process has died until after the core handler is
> >finished, and if the unity8 proces
On 10.01.2014 23:58, Steve Langasek wrote:
Oh, ok - yes, dying with SIGSEGV after receiving SIGTERM from upstart would
certainly trigger that behavior.
Is the SIGTERM being sent because the user session is exiting? If so,
overriding the kill timeout may not be enough, because upstart will also
25 matches
Mail list logo
