From: "Mingde (Matthew) Zeng" <matthew.zeng@windriver.com>
To: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 1/9] poppler: upgrade 0.82.0 -> 0.84.0
Date: Mon, 13 Jan 2020 15:20:52 -0500 [thread overview]
Message-ID: <87k15vw1jv.fsf@windriver.com> (raw)
In-Reply-To: <CALbNGRT-yQLsGTLsSTJzbhU5b6zzLxHmb6A2wi-pDfmZt-4_8A@mail.gmail.com>
>> Have you by chance tried to add ptest coverage for poppler?
>> If not, Matthew may do that.
>>
>>
> Have not done any ptest on this - just some runtime tests on target with evince
>
> Andreas
```
$ make test
Running tests...
Test project /home/mzeng/code/poppler/build
Start 1: check_qt5_attachments
1/21 Test #1: check_qt5_attachments ............***Failed 2.47 sec
Start 2: check_qt5_dateConversion
2/21 Test #2: check_qt5_dateConversion ......... Passed 0.58 sec
...
```
Poppler's `make test` runs tests from the `/build/qt5/tests` directory, which apparently are relying on qt5.
```
/****************************************************************************
** Meta object code from reading C++ file 'check_attachments.cpp'
**
** Created by: The Qt Meta Object Compiler version 67 (Qt 5.14.0)
**
** WARNING! All changes made in this file will be lost!
*****************************************************************************/
#include <memory>
#include <QtCore/qbytearray.h>
#include <QtCore/qmetatype.h>
...
```
Is it worth it to write a ptest and sort out the meta-qt5 layer?
Matthew
next prev parent reply other threads:[~2020-01-13 20:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 21:05 [PATCH 1/9] poppler: upgrade 0.82.0 -> 0.84.0 Andreas Müller
2020-01-09 21:05 ` [PATCH 2/9] xfce4-terminal: upgrade 0.8.9 -> 0.8.9.1 Andreas Müller
2020-01-09 21:05 ` [PATCH 3/9] mutter: upgrade 3.34.2 -> 3.34.3 Andreas Müller
2020-01-09 21:05 ` [PATCH 4/9] gnome-shell: " Andreas Müller
2020-01-09 21:05 ` [PATCH 5/9] evolution-data-server: " Andreas Müller
2020-01-09 21:05 ` [PATCH 6/9] gjs: upgrade 1.58.3 -> 1.58.4 Andreas Müller
2020-01-09 21:05 ` [PATCH 7/9] gnome-desktop3: upgrade 3.34.2 -> 3.34.3 Andreas Müller
2020-01-09 21:05 ` [PATCH 8/9] libsigc++-3: upgrade 3.0.0 -> 3.0.2 Andreas Müller
2020-01-09 22:07 ` Khem Raj
2020-01-09 22:33 ` Andreas Müller
2020-01-09 21:05 ` [PATCH 9/9] libsigc++-3: let meson build Andreas Müller
2020-01-09 22:01 ` [PATCH 1/9] poppler: upgrade 0.82.0 -> 0.84.0 Randy MacLeod
2020-01-09 22:24 ` Andreas Müller
2020-01-13 20:20 ` Mingde (Matthew) Zeng [this message]
2020-01-13 20:34 ` Randy MacLeod
2020-01-14 0:42 ` Randy MacLeod
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k15vw1jv.fsf@windriver.com \
--to=matthew.zeng@windriver.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.