Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1020306 > unrolled thread

Bug#966923: gjs: FTBFS: tests failed

Started byLucas Nussbaum <lucas@debian.org>
First post2020-08-03 11:10 +0200
Last post2020-08-20 20:00 +0200
Articles 3 — 3 participants

Back to article view | Back to linux.debian.bugs.dist


Contents

  Bug#966923: gjs: FTBFS: tests failed Lucas Nussbaum <lucas@debian.org> - 2020-08-03 11:10 +0200
    Bug#966923: meson: 0.55.0 considers TAP "ok # SKIP" to be a failure Simon McVittie <smcv@debian.org> - 2020-08-03 13:20 +0200
    Bug#966923: meson: diff for NMU version 0.55.0-2.1 Iain Lane <iain@orangesquash.org.uk> - 2020-08-20 20:00 +0200

#1020306 — Bug#966923: gjs: FTBFS: tests failed

FromLucas Nussbaum <lucas@debian.org>
Date2020-08-03 11:10 +0200
SubjectBug#966923: gjs: FTBFS: tests failed
Message-ID<AzEDO-18f-47@gated-at.bofh.it>
Source: gjs
Version: 1.64.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> obj-$(dpkg-architecture -q DEB_HOST_GNU_TYPE)/gjs-console -c 'print("Smoke-test OK")'
> Smoke-test OK
> mkdir -p -m700 debian/temp-home
> mkdir -p -m700 debian/temp-home/run
> env \
> 	-u XDG_CACHE_HOME \
> 	-u XDG_CONFIG_HOME \
> 	-u XDG_CONFIG_DIRS \
> 	-u XDG_DATA_HOME \
> 	-u XDG_DATA_DIRS \
> 	HOME=/<<PKGBUILDDIR>>/debian/temp-home \
> 	XDG_RUNTIME_DIR=/<<PKGBUILDDIR>>/debian/temp-home/run \
> 	TZ=UTC \
> xvfb-run -a \
> meson test -C /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu --timeout-multiplier 4
> ninja: Entering directory `/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
> ninja: no work to do.
>  1/53 gjs:C / API tests                 FAIL           2.24s (exit status 0)
>  2/53 gjs:Scripts / CommandLine         FAIL           1.23s (exit status 0)
>  3/53 gjs:Scripts / Warnings            OK             0.18s
>  4/53 gjs:JS / self                     OK             0.13s
>  5/53 gjs:JS / ByteArray                OK             0.07s
>  6/53 gjs:JS / Exceptions               OK             0.12s
>  7/53 gjs:JS / Format                   OK             0.12s
>  8/53 gjs:JS / Fundamental              OK             0.07s
>  9/53 gjs:JS / Gettext                  OK             0.07s
> 10/53 gjs:JS / GIMarshalling            FAIL           0.22s (exit status 0)
> 11/53 gjs:JS / Gio                      OK             0.12s
> 12/53 gjs:JS / GLib                     OK             0.12s
> 13/53 gjs:JS / GObject                  OK             0.07s
> 14/53 gjs:JS / GObjectClass             OK             0.17s
> 15/53 gjs:JS / GObjectInterface         OK             0.12s
> 16/53 gjs:JS / GTypeClass               OK             0.13s
> 17/53 gjs:JS / Importer                 OK             0.12s
> 18/53 gjs:JS / Introspection            OK             0.27s
> 19/53 gjs:JS / Lang                     OK             0.13s
> 20/53 gjs:JS / LegacyByteArray          OK             0.12s
> 21/53 gjs:JS / LegacyClass              OK             0.12s
> 22/53 gjs:JS / LegacyGObject            OK             0.17s
> 23/53 gjs:JS / Mainloop                 OK             0.22s
> 24/53 gjs:JS / Namespace                OK             0.07s
> 25/53 gjs:JS / Package                  OK             0.12s
> 26/53 gjs:JS / ParamSpec                OK             0.07s
> 27/53 gjs:JS / Regress                  FAIL           0.17s (exit status 0)
> 28/53 gjs:JS / Signals                  OK             0.12s
> 29/53 gjs:JS / System                   OK             0.12s
> 30/53 gjs:JS / Tweener                  OK             0.12s
> 31/53 gjs:JS / WarnLib                  OK             0.12s
> 32/53 gjs:JS / Cairo                    OK             0.27s
> 33/53 gjs:JS / Gtk3                     FAIL           0.22s (exit status 0)
> 34/53 gjs:JS / GObjectDestructionAccess OK             0.17s
> 35/53 gjs:JS / LegacyGtk                OK             0.27s
> 36/53 gjs:dbus / GDBus                  OK             0.17s
> 37/53 gjs:Debugger / backtrace command  OK             0.07s
> 38/53 gjs:Debugger / breakpoint command OK             0.07s
> 39/53 gjs:Debugger / continue command   OK             0.07s
> 40/53 gjs:Debugger / delete command     OK             0.07s
> 41/53 gjs:Debugger / detach command     OK             0.07s
> 42/53 gjs:Debugger / down-up command    OK             0.07s
> 43/53 gjs:Debugger / finish command     OK             0.07s
> 44/53 gjs:Debugger / frame command      OK             0.07s
> 45/53 gjs:Debugger / keys command       OK             0.07s
> 46/53 gjs:Debugger / next command       OK             0.03s
> 47/53 gjs:Debugger / print command      OK             0.07s
> 48/53 gjs:Debugger / quit command       OK             0.07s
> 49/53 gjs:Debugger / return command     OK             0.07s
> 50/53 gjs:Debugger / set command        OK             0.07s
> 51/53 gjs:Debugger / step command       OK             0.07s
> 52/53 gjs:Debugger / throw command      OK             0.07s
> 53/53 gjs:Debugger / until command      OK             0.07s
> 
> Ok:                 48  
> Expected Fail:      0   
> Fail:               5   
> Unexpected Pass:    0   
> Skipped:            0   
> Timeout:            0   
> 
> Full log written to /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu/meson-logs/testlog.txt
> make[1]: *** [debian/rules:31: override_dh_auto_test] Error 5

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/gjs_1.64.3-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.

[toc] | [next] | [standalone]


#1020353 — Bug#966923: meson: 0.55.0 considers TAP "ok # SKIP" to be a failure

FromSimon McVittie <smcv@debian.org>
Date2020-08-03 13:20 +0200
SubjectBug#966923: meson: 0.55.0 considers TAP "ok # SKIP" to be a failure
Message-ID<AzGFz-2lw-3@gated-at.bofh.it>
In reply to#1020306

[Multipart message — attachments visible in raw view] — view raw

Control: retitle -1 meson: 0.55.0 considers TAP "ok # SKIP" to be a failure
Control: reassign -1 meson 0.55.0-2
Control: affects -1 + gjs
Control: forwarded -1 https://github.com/mesonbuild/meson/issues/7515
Control: tags -1 + upstream

On Mon, 03 Aug 2020 at 10:51:25 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
...
> > meson test -C /<<PKGBUILDDIR>>/obj-x86_64-linux-gnu --timeout-multiplier 4
...
> > 10/53 gjs:JS / GIMarshalling            FAIL           0.22s (exit status 0)
...
> > 27/53 gjs:JS / Regress                  FAIL           0.17s (exit status 0)
...
> > 33/53 gjs:JS / Gtk3                     FAIL           0.22s (exit status 0)

What is happening here was obscured by gjs not printing the output of
failing tests to the buildd log, but if you apply the attached gjs.diff,
you can see that the affected tests are those that have some steps that
are skipped.

Reproducer:

$ cat meson.build
project('debian-bug-966923')
foreach test_name : ['pass.sh', 'skip.sh']
  test(test_name, files(test_name), protocol : 'tap')
endforeach
$ cat pass.sh
#!/bin/sh
echo "ok 1"
echo "ok 2"
exit 0
$ cat skip.sh
#!/bin/sh
echo "ok 1 # SKIP cannot actually do this"
echo "ok 2"
exit 0
$ chmod +x pass.sh skip.sh
$ meson _build
$ meson test -C _build

Regards,
    smcv

[toc] | [prev] | [next] | [standalone]


#1022229 — Bug#966923: meson: diff for NMU version 0.55.0-2.1

FromIain Lane <iain@orangesquash.org.uk>
Date2020-08-20 20:00 +0200
SubjectBug#966923: meson: diff for NMU version 0.55.0-2.1
Message-ID<AFX0Z-2qV-3@gated-at.bofh.it>
In reply to#1020306

[Multipart message — attachments visible in raw view] — view raw

Control: tags 966923 + patch
Control: tags 966923 + pending
Control: tags 968704 + pending

Dear maintainer,

I'm sponsoring an NMU for meson (versioned as 0.55.0-2.1) and uploaded
it without delay, after Marco spoke to Martin. Hopefully this doesn't
cause you too much trouble - the skip bug is blocking our work on
updating GNOME to 3.38 so we need this fixed at least in unstable.

Regards,

-- 
Iain Lane                                  [ iain@orangesquash.org.uk ]
Debian Developer                                   [ laney@debian.org ]
Ubuntu Developer                                   [ laney@ubuntu.com ]

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web