From: Eloitor <Eloitor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gdk-pixbuf: update to 2.42.10.
Date: Fri, 25 Nov 2022 12:53:10 +0100 [thread overview]
Message-ID: <20221125115310.RFRQYJaxWsChoB6c61NH7wcZVaee4N0QbNwZLROO440@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40758@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2180 bytes --]
New comment by Eloitor on void-packages repository
https://github.com/void-linux/void-packages/pull/40758#issuecomment-1327381613
Comment:
I don't understand why some checks fail. It worked locally...
```
=> gdk-pixbuf-2.42.10_1: running do_check ...
ninja: Entering directory `build'
[0/1] Running all tests.
1/22 gdk-pixbuf:conform / pixbuf-construction OK 0.03s
2/22 gdk-pixbuf:format / animation OK 0.03s
3/22 gdk-pixbuf:conform / pixbuf-icon-serialize OK 0.03s
4/22 gdk-pixbuf:io / pixbuf-threads OK 0.03s
5/22 gdk-pixbuf:io / pixbuf-gif OK 0.02s
6/22 gdk-pixbuf:io / pixbuf-icc OK 0.02s
7/22 gdk-pixbuf:io / pixbuf-dpi OK 0.02s
8/22 gdk-pixbuf:format / pixbuf-pixdata OK 0.02s
9/22 gdk-pixbuf:io / pixbuf-stream OK 0.05s
10/22 gdk-pixbuf:io / pixbuf-resource OK 0.04s
11/22 gdk-pixbuf:format / pixbuf-gif-circular-table OK 0.03s
12/22 gdk-pixbuf:io / pixbuf-save OK 0.02s
13/22 gdk-pixbuf:conform / pixbuf-readonly-to-mutable OK 0.02s
14/22 gdk-pixbuf:ops / pixbuf-composite OK 0.01s
15/22 gdk-pixbuf:ops / pixbuf-scale OK 0.04s
16/22 gdk-pixbuf:ops / pixbuf-scale-two-step OK 0.04s
17/22 gdk-pixbuf:slow / pixbuf-area-updated OK 0.08s
18/22 gdk-pixbuf:format / pixbuf-short-gif-write OK 0.21s
19/22 gdk-pixbuf:conform / pixbuf-reftest OK 0.24s
20/22 gdk-pixbuf:security / cve-2015-4491 OK 0.35s
21/22 gdk-pixbuf:conform+slow / pixbuf-fail OK 5.06s
22/22 gdk-pixbuf:format / pixbuf-jpeg OK 6.35s
Ok: 22
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 0
Timeout: 0
```
next prev parent reply other threads:[~2022-11-25 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 11:45 [PR PATCH] " Eloitor
2022-11-25 11:51 ` Eloitor
2022-11-25 11:53 ` Eloitor [this message]
2022-11-25 14:00 ` icp1994
2022-11-25 14:08 ` Eloitor
2022-11-30 11:15 ` [PR PATCH] [Updated] " Eloitor
2023-03-01 5:18 ` github-actions
2023-03-01 12:44 ` [PR PATCH] [Updated] " Eloitor
2023-03-04 8:56 ` biopsin
2023-03-30 20:54 ` paper42
2023-03-30 20:54 ` [PR PATCH] [Closed]: " paper42
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=20221125115310.RFRQYJaxWsChoB6c61NH7wcZVaee4N0QbNwZLROO440@z \
--to=eloitor@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).