Github messages for voidlinux
 help / color / mirror / Atom feed
From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] kitinerary tests failing on all archectures
Date: Mon, 18 Apr 2022 22:49:28 +0200	[thread overview]
Message-ID: <20220418204928.M-w6wgqat8OyKFTlwWCeHr_JRWxEdyQBayGJILsOMLc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36734@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1328 bytes --]

Closed issue by oreo639 on void-packages repository

https://github.com/void-linux/void-packages/issues/36734

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  Void 5.15.32_1 x86_64 GenuineIntel uptodate hold rrrmFFFFFFFFFFFFFFFF
  *output of ``xuname`` (part of xtools)*
* package:  `kitinerary-21.12.3_1`
  *affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``

### Expected behavior
Tests succeed when performing:
`./xbps-src check kitinerary`

### Actual behavior
`Test #31: calendarhandlertest` fails due to the ics file generated not entirely matching what was expected. (most of the differences are just caps instead of lower case or extra information)
Here is a log of the full output:
https://github.com/void-linux/void-packages/runs/6053085034?check_suite_focus=true
(in the log above the issue occurred in the poppler PR, but I can reproduce this issue in the master branch even after clearing out the builddir)

### Steps to reproduce the behavior
`./xbps-src check kitinerary`

Not sure how best to fix this. (the best I can think of would probably be to just disable the tests until the next release)

      reply	other threads:[~2022-04-18 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17 10:54 [ISSUE] " oreo639
2022-04-18 20:49 ` paper42 [this message]

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=20220418204928.M-w6wgqat8OyKFTlwWCeHr_JRWxEdyQBayGJILsOMLc@z \
    --to=paper42@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).