** Changed in: mir
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
This bug was fixed in the package mir - 0.26.0+17.04.20170126.3-0ubuntu1
---
mir (0.26.0+17.04.20170126.3-0ubuntu1) zesty; urgency=medium
[ Daniel van Vugt ]
* New upstream release 0.26.0 (https://launchpad.net/mir/+milestone/0.26.0)
- ABI summary:
. mirclient ABI
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2369
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
** Changed in: mir
Milestone: 1.0.0 => 0.26.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
Fix committed into lp:mir at revision 3949, scheduled for release in
mir, milestone 1.0.0
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Changed in: mir
Milestone: 0.26.0 => 1.0.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
** Branch linked: lp:~vanvugt/mir/remove-input-resampling-standlone
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
** Changed in: mir
Milestone: None => 0.26.0
** Changed in: mir
Status: Triaged => In Progress
** Branch linked: lp:~vanvugt/mir/remove-input-resampling
** Branch linked: lp:~vanvugt/mir/remove-input-resampling
--
You received this bug notification because you are a member of
10:15:27 Expected: to be called between 20 and 180 times
10:15:27 Actual: called 181 times - over-saturated and active
10:15:27
10:15:27 GMOCK WARNING:
10:15:27 Uninteresting mock function call - returning directly.
10:15:27 Function call: handle_input(touch_event(when=3725515999186980
Yeah this failure has become more of a problem with the CapnProto event
code. Prior to that it wasn't failing for months at a time.
Long term we expect input resampling functionality to get dropped from
Mir, and this test case with it. Because client-side vsync should allow
Unity8 to use the
12:32:46 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
12:32:46 11: [2016-12-13 12:32:46.184830] mirserver: Starting
12:32:46 11: [2016-12-13 12:32:46.188127] mirserver: Selected driver:
mir:stub-graphics (version 0.26.0)
12:32:46 11: [2016-12-13 12:32:46.501072] mirserver: Using
And again:
06:27:08 11:
/<>/mir-0.25.0+xenial3115bzr3852/tests/acceptance-tests/test_client_input.cpp:667:
Failure
06:27:08 11: Mock function called more times than expected - returning directly.
06:27:08 11: Function call: handle_input(touch_event(when=1476068422342080
(39.829455ms ago),
And again:
08:36:20 11:
/<>/mir-0.25.0+xenial3097bzr3867/tests/acceptance-tests/test_client_input.cpp:667:
Failure
08:36:20 11: Mock function called more times than expected - returning directly.
08:36:20 11: Function call: handle_input(touch_event(when=2424279781829824
(29.428950ms ago),
Again:
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2970/consoleFull
12:05:28 9: Actual function call count doesn't match EXPECT_CALL(first_client,
handle_input(_))...
12:05:28 9: Expected: to be called between 20 and 180 times
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2209
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
End of the day and I have better news now:
The first prototype of client-side vsync is working well and I'm hopeful
to get it into Mir 0.26. With some luck that will solve the
incompatibility between Qt's input resampler logic and our nested
architecture. So then if Unity8 is able to use Qt's
Brandon said he had plans to continue with Capn Proto work that would
solve the performance problems it has introduced here. So this failure
should go away when the Capn Proto work is finished. Although I'm not
too familiar with the changes Anpok also made to the test itself. It was
pretty quiet
18:00:31
/<>/mir-0.25.0+yakkety2832bzr3817/tests/acceptance-tests/test_client_input.cpp:636:
Failure
18:00:31 Value of: first_client.all_events_received.wait_for(120s)
18:00:31 Actual: false
18:00:31 Expected: true
18:00:31
Reopened because it's happening again:
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=amd64,compiler=clang,platform=mesa,release=yakkety/2804/consoleFull
Although possibly for different reasons now (anpok modified the test and
brandon made the event system slower and more likely to
** Branch linked: lp:~ci-train-bot/mir/mir-ubuntu-zesty-2180
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
I think the attached recent branches have solved this in general. It's
still failing in Brandon's branches only, but probably for good reason.
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: mir
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Branch linked: lp:~vanvugt/mir/loosen-1570698
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
** Changed in: mir
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
Maybe fixed? Not yet sure if that branch just landed is sufficient.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.25.0
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Branch linked: lp:~vanvugt/mir/catchup-1570698
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
** Branch linked: lp:~vanvugt/mir/improve-1570698
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
** Changed in: mir
Milestone: None => 0.25.0
** Changed in: mir
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI
** Changed in: mir
Milestone: 0.25.0 => None
** Changed in: mir
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
And again: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1474/console
and: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1475/console
Raising importance to high.
** Changed
Again: https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1476/consoleFull
10:15:01 11: [ RUN ] TestClientInput.receives_one_touch_event_per_frame
10:15:01 11: [2016-07-08 10:15:01.272873] mirserver: Starting
10:15:01 11: [2016-07-08
** Changed in: mir
Milestone: 0.24.0 => 0.25.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
Another instance:
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1221/consoleFull
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Changed in: mir (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
This bug was fixed in the package mir - 0.22.1+16.04.20160516.2-0ubuntu2
---
mir (0.22.1+16.04.20160516.2-0ubuntu2) yakkety; urgency=medium
[ Dimitri John Ledkov ]
* Fix FTBFS error: call of overloaded ‘abs(float)’ is ambiguous, by
including cmath c++ header.
-- Łukasz
Brandon: This actually only happens once or twice a week or so for the
rest of us. If your branch hits it more often that might indicate that
branch needs fixing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Ive been getting this as well here:
https://code.launchpad.net/~brandontschaefer/mir/mir-event-capnproto/+merge/290760
Nice to see i might not be 100% my fault. Thought the fix should be
moving away from real time for the test.
--
You received this bug notification because you are a member of
https://mir-jenkins.ubuntu.com/job/build-2-binpkg-
mir/arch=i386,compiler=gcc,platform=mesa,release=xenial/1015/consoleFull
...
22:06:59 11: Expected: to be called between 50 and 150 times
22:06:59 11: Actual: called 167 times - over-saturated and active
22:06:59 11:
** Changed in: mir
Milestone: 0.23.0 => 0.24.0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in
Still happening in CI yesterday and today. Needs fixing more.
Although I suspect the test is theoretically correct, the main issue is
one or two CI machines are often too slow to do time-sensitive tests.
** Changed in: mir
Status: Fix Committed => Triaged
** Changed in: mir
Fix committed into lp:mir at revision None, scheduled for release in
mir, milestone 0.22.0
** Changed in: mir
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
** Branch linked: lp:~vanvugt/mir/fix-1570698
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1570698
Title:
CI failure in TestClientInput.receives_one_touch_event_per_frame
** Changed in: mir
Milestone: None => 0.22.0
** Changed in: mir
Importance: Undecided => Medium
** Changed in: mir
Status: New => In Progress
** Changed in: mir
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: mir (Ubuntu)
Importance: Undecided
45 matches
Mail list logo
