Your message dated Tue, 8 Jan 2019 21:21:33 +0100
with message-id <20190108202133.rhndoayl3ozgs...@xanadu.blop.info>
and subject line Re: libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1
returned exit code 2
has caused the Debian Bug report #917718,
regarding libuv1: FTBFS: dh_auto_test: make -j1 check VERBOSE=1 returned exit
code 2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
917718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917718
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libuv1
Version: 1.24.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<<PKGBUILDDIR>>'
> 1..343
> ok 1 - platform_output
> # Output from process `platform_output`:
> # uv_get_process_title: /<<PKGBUILDDIR>>/test/.libs/run-tests
> # uv_cwd: /<<PKGBUILDDIR>>
> # uv_resident_set_memory: 1069056
> # uv_uptime: 7932.000000
> # uv_getrusage:
> # user: 0 sec 0 microsec
> # system: 0 sec 0 microsec
> # page faults: 0
> # maximum resident set size: 1044
> # uv_cpu_info:
> # model: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
> # speed: 2500
> # times.sys: 6262800
> # times.user: 60641700
> # times.idle: 10290400
> # times.irq: 0
> # times.nice: 0
> # model: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
> # speed: 2500
> # times.sys: 6210200
> # times.user: 59260500
> # times.idle: 11656300
> # times.irq: 0
> # times.nice: 0
> # uv_interface_addresses:
> # name: lo
> # internal: 1
> # physical address: 00:00:00:00:00:00
> # address: 127.0.0.1
> # netmask: 255.0.0.0
> # name: eth0
> # internal: 0
> # physical address: 06:c0:2d:38:cd:2c
> # address: 172.31.2.71
> # netmask: 255.255.240.0
> # name: lo
> # internal: 1
> # physical address: 00:00:00:00:00:00
> # address: ::1
> # netmask: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
> # name: eth0
> # internal: 0
> # physical address: 06:c0:2d:38:cd:2c
> # address: fe80::4c0:2dff:fe38:cd2c
> # netmask: ffff:ffff:ffff:ffff::
> # uv_os_get_passwd:
> # euid: 1001
> # gid: 1001
> # username: user42
> # shell:
> # home directory: /home/user42
> # uv_os_getpid: 14358
> # uv_os_getppid: 14344
> ok 2 - active
> ok 3 - async
> ok 4 - async_null_cb
> ok 5 - async_ref
> ok 6 - barrier_1
> ok 7 - barrier_2
> ok 8 - barrier_3
> ok 9 - barrier_serial_thread
> ok 10 - barrier_serial_thread_single
> ok 11 - callback_stack
> ok 12 - check_ref
> ok 13 - close_fd
> ok 14 - close_order
> ok 15 - closed_fd_events
> ok 16 - condvar_1
> ok 17 - condvar_2
> ok 18 - condvar_3
> ok 19 - condvar_4
> ok 20 - condvar_5
> ok 21 - connect_unspecified
> ok 22 - connection_fail
> ok 23 - connection_fail_doesnt_auto_close
> ok 24 - cwd_and_chdir
> ok 25 - default_loop_close
> ok 26 - delayed_accept
> ok 27 - dlerror
> ok 28 - eintr_handling
> ok 29 - embed
> ok 30 - emfile
> ok 31 - env_vars
> ok 32 - error_message
> ok 33 - fork_fs_events_child
> ok 34 - fork_fs_events_child_dir
> ok 35 - fork_fs_events_file_parent_child
> ok 36 - fork_signal_to_child
> ok 37 - fork_signal_to_child_closed
> ok 38 - fork_socketpair
> ok 39 - fork_socketpair_started
> ok 40 - fork_threadpool_queue_work_simple
> ok 41 - fork_timer
> ok 42 - fs_access
> ok 43 - fs_async_dir
> ok 44 - fs_async_sendfile
> ok 45 - fs_chmod
> ok 46 - fs_chown
> ok 47 - fs_copyfile
> ok 48 - fs_event_close_in_callback
> ok 49 - fs_event_close_with_pending_event
> ok 50 - fs_event_error_reporting
> ok 51 - fs_event_getpath
> ok 52 - fs_event_immediate_close
> ok 53 - fs_event_no_callback_after_close
> ok 54 - fs_event_no_callback_on_close
> ok 55 - fs_event_ref
> ok 56 - fs_event_start_and_close
> ok 57 - fs_event_watch_dir
> ok 58 - fs_event_watch_dir_recursive # SKIP Recursive directory watching not
> supported on this platform.
> ok 59 - fs_event_watch_file
> ok 60 - fs_event_watch_file_current_dir
> ok 61 - fs_event_watch_file_exact_path
> ok 62 - fs_event_watch_file_twice
> ok 63 - fs_event_watch_invalid_path
> ok 64 - fs_file_async
> ok 65 - fs_file_loop
> ok 66 - fs_file_nametoolong
> ok 67 - fs_file_noent
> ok 68 - fs_file_open_append
> ok 69 - fs_file_pos_after_op_with_offset
> ok 70 - fs_file_sync
> ok 71 - fs_file_write_null_buffer
> ok 72 - fs_fstat
> ok 73 - fs_futime
> ok 74 - fs_mkdtemp
> ok 75 - fs_null_req
> ok 76 - fs_open_dir
> ok 77 - fs_partial_read
> ok 78 - fs_partial_write
> ok 79 - fs_poll
> ok 80 - fs_poll_getpath
> ok 81 - fs_poll_ref
> ok 82 - fs_read_dir
> ok 83 - fs_read_file_eof
> ok 84 - fs_read_write_null_arguments
> ok 85 - fs_readlink
> ok 86 - fs_realpath
> ok 87 - fs_rename_to_existing_file
> ok 88 - fs_scandir_empty_dir
> ok 89 - fs_scandir_file
> ok 90 - fs_scandir_non_existent_dir
> ok 91 - fs_stat_missing_path
> ok 92 - fs_symlink
> ok 93 - fs_symlink_dir
> ok 94 - fs_unlink_readonly
> ok 95 - fs_utime
> ok 96 - fs_write_alotof_bufs
> ok 97 - fs_write_alotof_bufs_with_offset
> ok 98 - fs_write_multiple_bufs
> ok 99 - get_currentexe
> ok 100 - get_loadavg
> ok 101 - get_memory
> ok 102 - get_osfhandle_valid_handle
> not ok 103 - get_passwd
> # exit code 6
> # Output from process `get_passwd`:
> # Assertion failed in test/test-get-passwd.c on line 41: len > 0
> ok 104 - getaddrinfo_basic
> ok 105 - getaddrinfo_basic_sync
> ok 106 - getaddrinfo_concurrent
> ok 107 - getaddrinfo_fail
> ok 108 - getaddrinfo_fail_sync
> ok 109 - gethostname
> ok 110 - getnameinfo_basic_ip4
> ok 111 - getnameinfo_basic_ip4_sync
> ok 112 - getnameinfo_basic_ip6 # SKIP DNS request disabled in ipv6 test
> ok 113 - getsockname_tcp
> ok 114 - getsockname_udp
> ok 115 - getters_setters
> ok 116 - handle_fileno
> ok 117 - handle_type_name
> ok 118 - has_ref
> ok 119 - homedir
> ok 120 - hrtime
> ok 121 - idle_ref
> ok 122 - idle_starvation
> ok 123 - idna_toascii
> ok 124 - ip4_addr
> ok 125 - ip6_addr_link_local
> ok 126 - ip6_pton
> ok 127 - ipc_closed_handle
> ok 128 - ipc_heavy_traffic_deadlock_bug
> ok 129 - ipc_listen_after_write
> ok 130 - ipc_listen_before_write
> ok 131 - ipc_send_recv_pipe
> ok 132 - ipc_send_recv_pipe_inprocess
> ok 133 - ipc_send_recv_tcp
> ok 134 - ipc_send_recv_tcp_inprocess
> ok 135 - ipc_tcp_connection
> ok 136 - kill
> ok 137 - kill_invalid_signum
> ok 138 - loop_alive
> ok 139 - loop_backend_timeout
> ok 140 - loop_close
> ok 141 - loop_configure
> ok 142 - loop_handles
> ok 143 - loop_instant_close
> ok 144 - loop_stop
> ok 145 - loop_update_time
> ok 146 - multiple_listen
> ok 147 - open_osfhandle_valid_handle
> ok 148 - pipe_bind_error_addrinuse
> ok 149 - pipe_bind_error_addrnotavail
> ok 150 - pipe_bind_error_inval
> ok 151 - pipe_close_stdout_read_stdin
> ok 152 - pipe_connect_bad_name
> ok 153 - pipe_connect_multiple
> ok 154 - pipe_connect_on_prepare
> ok 155 - pipe_connect_to_file
> ok 156 - pipe_getsockname
> ok 157 - pipe_getsockname_abstract
> ok 158 - pipe_getsockname_blocking
> ok 159 - pipe_listen_without_bind
> ok 160 - pipe_pending_instances
> ok 161 - pipe_ping_pong
> ok 162 - pipe_ping_pong_vec
> ok 163 - pipe_ref
> ok 164 - pipe_ref2
> ok 165 - pipe_ref3
> ok 166 - pipe_ref4
> ok 167 - pipe_sendmsg
> ok 168 - pipe_server_close
> ok 169 - pipe_set_chmod
> ok 170 - pipe_set_non_blocking
> ok 171 - poll_bad_fdtype
> ok 172 - poll_close
> ok 173 - poll_close_doesnt_corrupt_stack # SKIP Test only relevant on Windows
> ok 174 - poll_closesocket # SKIP Test only relevant on Windows
> ok 175 - poll_duplex
> ok 176 - poll_nested_epoll
> ok 177 - poll_oob
> ok 178 - poll_unidirectional
> ok 179 - prepare_ref
> ok 180 - process_priority
> ok 181 - process_ref
> ok 182 - process_title
> ok 183 - process_title_threadsafe
> ok 184 - queue_foreach_delete
> ok 185 - ref
> ok 186 - req_type_name
> ok 187 - run_nowait
> ok 188 - run_once
> ok 189 - semaphore_1
> ok 190 - semaphore_2
> ok 191 - semaphore_3
> ok 192 - shutdown_close_pipe
> ok 193 - shutdown_close_tcp
> ok 194 - shutdown_eof
> ok 195 - shutdown_twice
> ok 196 - signal_multiple_loops
> ok 197 - socket_buffer_size
> ok 198 - spawn_and_kill
> ok 199 - spawn_and_kill_with_std
> ok 200 - spawn_and_ping
> ok 201 - spawn_auto_unref
> ok 202 - spawn_closed_process_io
> ok 203 - spawn_detached
> ok 204 - spawn_exit_code
> ok 205 - spawn_fails
> ok 206 - spawn_fails_check_for_waitpid_cleanup
> ok 207 - spawn_fs_open
> ok 208 - spawn_ignored_stdio
> ok 209 - spawn_inherit_streams
> ok 210 - spawn_preserve_env
> ok 211 - spawn_quoted_path # SKIP Test for Windows
> ok 212 - spawn_reads_child_path
> ok 213 - spawn_setgid_fails
> ok 214 - spawn_setuid_fails
> ok 215 - spawn_setuid_setgid # SKIP It should be run as root user
> ok 216 - spawn_stdin
> ok 217 - spawn_stdio_greater_than_3
> ok 218 - spawn_stdout
> ok 219 - spawn_stdout_and_stderr_to_file
> ok 220 - spawn_stdout_and_stderr_to_file2
> ok 221 - spawn_stdout_and_stderr_to_file_swap
> ok 222 - spawn_stdout_to_file
> ok 223 - spawn_tcp_server
> ok 224 - stdio_over_pipes
> ok 225 - sys_error
> ok 226 - tcp6_ping_pong
> ok 227 - tcp6_ping_pong_vec
> ok 228 - tcp_alloc_cb_fail
> ok 229 - tcp_bind6_error_addrinuse
> ok 230 - tcp_bind6_error_addrnotavail
> ok 231 - tcp_bind6_error_fault
> ok 232 - tcp_bind6_error_inval
> ok 233 - tcp_bind6_localhost_ok
> ok 234 - tcp_bind_error_addrinuse
> ok 235 - tcp_bind_error_addrnotavail_1
> ok 236 - tcp_bind_error_addrnotavail_2
> ok 237 - tcp_bind_error_fault
> ok 238 - tcp_bind_error_inval
> ok 239 - tcp_bind_invalid_flags
> ok 240 - tcp_bind_localhost_ok
> ok 241 - tcp_bind_writable_flags
> ok 242 - tcp_close
> ok 243 - tcp_close_accept
> ok 244 - tcp_close_while_connecting
> ok 245 - tcp_connect_error_after_write
> ok 246 - tcp_connect_error_fault
> ok 247 - tcp_connect_timeout
> ok 248 - tcp_create_early
> ok 249 - tcp_create_early_accept
> ok 250 - tcp_create_early_bad_bind
> ok 251 - tcp_create_early_bad_domain
> ok 252 - tcp_flags
> ok 253 - tcp_listen_without_bind
> ok 254 - tcp_oob
> ok 255 - tcp_open
> ok 256 - tcp_open_bound
> ok 257 - tcp_open_connected
> ok 258 - tcp_open_twice
> ok 259 - tcp_ping_pong
> ok 260 - tcp_ping_pong_vec
> ok 261 - tcp_read_stop
> ok 262 - tcp_ref
> ok 263 - tcp_ref2
> ok 264 - tcp_ref2b
> ok 265 - tcp_ref3
> ok 266 - tcp_ref4
> ok 267 - tcp_shutdown_after_write
> ok 268 - tcp_try_write
> ok 269 - tcp_unexpected_read
> ok 270 - tcp_write_after_connect
> ok 271 - tcp_write_fail
> ok 272 - tcp_write_queue_order
> ok 273 - tcp_write_ready
> ok 274 - tcp_write_to_half_open_connection
> ok 275 - tcp_writealot
> ok 276 - thread_create
> ok 277 - thread_equal
> ok 278 - thread_local_storage
> ok 279 - thread_mutex
> ok 280 - thread_mutex_recursive
> ok 281 - thread_rwlock
> ok 282 - thread_rwlock_trylock
> ok 283 - thread_stack_size
> ok 284 - threadpool_cancel_fs
> ok 285 - threadpool_cancel_getaddrinfo
> ok 286 - threadpool_cancel_getnameinfo
> ok 287 - threadpool_cancel_single
> ok 288 - threadpool_cancel_work
> ok 289 - threadpool_multiple_event_loops
> ok 290 - threadpool_queue_work_einval
> ok 291 - threadpool_queue_work_simple
> ok 292 - timer
> ok 293 - timer_again
> ok 294 - timer_early_check
> ok 295 - timer_from_check
> ok 296 - timer_huge_repeat
> ok 297 - timer_huge_timeout
> ok 298 - timer_init
> ok 299 - timer_null_callback
> ok 300 - timer_order
> ok 301 - timer_ref
> ok 302 - timer_ref2
> ok 303 - timer_run_once
> ok 304 - timer_start_twice
> ok 305 - tmpdir
> ok 306 - tty # SKIP Cannot open /dev/tty as read-only: No such device or
> address
> ok 307 - tty_file
> ok 308 - tty_pty
> ok 309 - udp_alloc_cb_fail
> ok 310 - udp_bind
> ok 311 - udp_bind_reuseaddr
> ok 312 - udp_create_early
> ok 313 - udp_create_early_bad_bind
> ok 314 - udp_create_early_bad_domain
> ok 315 - udp_dgram_too_big
> ok 316 - udp_dual_stack
> ok 317 - udp_ipv6_only
> ok 318 - udp_multicast_interface
> ok 319 - udp_multicast_interface6
> ok 320 - udp_multicast_join
> ok 321 - udp_multicast_join6
> ok 322 - udp_multicast_ttl
> ok 323 - udp_no_autobind
> ok 324 - udp_open
> ok 325 - udp_open_twice
> ok 326 - udp_options
> ok 327 - udp_options6
> ok 328 - udp_ref
> ok 329 - udp_ref2
> ok 330 - udp_ref3
> ok 331 - udp_send_and_recv
> ok 332 - udp_send_hang_loop
> ok 333 - udp_send_immediate
> ok 334 - udp_send_unreachable
> ok 335 - udp_try_send
> ok 336 - unref_in_prepare_cb
> ok 337 - utf8_decode1
> ok 338 - walk_handles
> ok 339 - watcher_cross_stop
> ok 340 - we_get_signal
> ok 341 - we_get_signal_one_shot
> ok 342 - we_get_signals
> ok 343 - we_get_signals_mixed
> FAIL: test/run-tests
> ======================================================
> 1 of 1 test failed
> Please report to https://github.com/libuv/libuv/issues
> ======================================================
> make[3]: *** [Makefile:4897: check-TESTS] Error 1
> make[3]: Leaving directory '/<<PKGBUILDDIR>>'
> make[2]: *** [Makefile:5157: check-am] Error 2
> make[2]: Leaving directory '/<<PKGBUILDDIR>>'
> dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
The full build log is available from:
http://aws-logs.debian.net/2018/12/29/libuv1_1.24.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Hi Dominique,
On 07/01/19 at 18:51 +0100, Dominique Dumont wrote:
> Hello
>
> On Sat, 29 Dec 2018 23:07:11 +0100 Lucas Nussbaum <lu...@debian.org> wrote:
> > not ok 103 - get_passwd
> > # exit code 6
> > # Output from process `get_passwd`:
> > # Assertion failed in test/test-get-passwd.c on line 41: len > 0
>
> Upstream asks:
> > That line asserts that the current user's shell in the password file is
> greater than zero. Do you happen to know what that particular password file
> entry looks like?
>
> Can you check the setup of the test system that showed this bug and reply on
> github ? [1]
I can confirm that this bug is a false positive: when I setup the build
environment, I created the user without a shell, which apparently caused
this failure.
I can confirm that it builds fine now. I'm closing the bug (and I'm
looking into other bugs I filed in the same process).
Sorry for the noise,
Lucas
--- End Message ---
