Merge lp:~mikemc/ubuntuone-client/skip-test-wait-no-more-events-blame-pb into lp:ubuntuone-client
Status: | Merged |
---|---|
Approved by: | Mike McCracken |
Approved revision: | 1378 |
Merged at revision: | 1370 |
Proposed branch: | lp:~mikemc/ubuntuone-client/skip-test-wait-no-more-events-blame-pb |
Merge into: | lp:ubuntuone-client |
Prerequisite: | lp:~mikemc/ubuntuone-client/accelerate-nirvana |
Diff against target: |
100 lines (+0/-73) 2 files modified
tests/platform/test_tools.py (+0/-16) ubuntuone/platform/tools/__init__.py (+0/-57) |
To merge this branch: | bzr merge lp:~mikemc/ubuntuone-client/skip-test-wait-no-more-events-blame-pb |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
dobey (community) | Approve | ||
Review via email: mp+142971@code.launchpad.net |
Commit message
- Remove unused and potentially incorrect wait_no_
Description of the change
- Remove unused and potentially incorrect wait_no_
On windows and darwin, twisted PB's connect_signal is async, so
wait_no_
'Event' signal, will not be connected until after the
event_q.
that we won't see that event.
Because wait_no_more_events internally waits for the signal to show,
it may not work as expected. Here's an incorrect sequence that happens every time in test_wait_
t:
0.00: call wait_no_
0.0?: it calls connect_signal, but doesn't wait for it to complete.
0.0?: it finishes, and registers check_last_event with the reactor to be called at 0.10.
0.0?: an event shows up sometime before the signal is connected.
0.10: check_last_event is called, and incorrectly returns True because the event
handler was not connected yet, so it saw no events.
0.1?: the event signal is potentially disconnected before it was
finished being connected (or not, it was still wrong)
So, because it's impossible to test on 2/3 of the platforms, and
doesn't appear to be used anywhere, I've removed wait_no_
The attempt to merge lp:~mikemc/ubuntuone-client/skip-test-wait-no-more-events-blame-pb into lp:ubuntuone-client failed. Below is the output from the failed tests.
/usr/bin/ gnome-autogen. sh MACRO_DIR, `m4'. unknown- linux-gnu unknown- linux-gnu
checking for autoconf >= 2.53...
testing autoconf2.50... not found.
testing autoconf... found 2.69
checking for automake >= 1.10...
testing automake-1.12... not found.
testing automake-1.11... found 1.11.6
checking for libtool >= 1.5...
testing libtoolize... found 2.4.2
checking for intltool >= 0.30...
testing intltoolize... found 0.50.2
checking for pkg-config >= 0.14.0...
testing pkg-config... found 0.26
checking for gtk-doc >= 1.0...
testing gtkdocize... found 1.18
Checking for required M4 macros...
Checking for forbidden M4 macros...
Processing ./configure.ac
Running libtoolize...
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
Running intltoolize...
Running gtkdocize...
Running aclocal-1.11...
Running autoconf...
Running autoheader...
Running automake-1.11...
Running ./configure --enable-gtk-doc --enable-debug ...
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking build system type... x86_64-
checking host system type... x86_64-
checking how to print strings... printf
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
check...