[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#27542] [PATCH] gnu: gcr: Enable working tests.
From: |
Roel Janssen |
Subject: |
[bug#27542] [PATCH] gnu: gcr: Enable working tests. |
Date: |
Mon, 03 Jul 2017 22:24:59 +0200 |
User-agent: |
mu4e 0.9.18; emacs 25.1.1 |
Kei Kebreau writes:
> address@hidden (Ludovic Courtès) writes:
>
>> Kei Kebreau <address@hidden> skribis:
>>
>>> address@hidden (Ludovic Courtès) writes:
>>>
>>>> Kei Kebreau <address@hidden> skribis:
>>>>
>>>>> address@hidden (Ludovic Courtès) writes:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Kei Kebreau <address@hidden> skribis:
>>>>>>
>>>>>>> * gnu/packages/patches/gcr-disable-failing-tests.patch,
>>>>>>> gnu/packages/patches/gcr-fix-collection-tests-to-work-with-gpg-21.patch:
>>>>>>> New files.
>>>>>>> * gnu/local.mk (dist_patch_DATA): Add patches.
>>>>>>> * gnu/packages/gnome.scm (gcr)[source]: Use patches.
>>>>>>> [arguments]: Enable tests.
>>>>>>
>>>>>> [...]
>>>>>>
>>>>>>> +++ b/gnu/packages/patches/gcr-disable-failing-tests.patch
>>>>>>> @@ -0,0 +1,127 @@
>>>>>>> +This patch removes a group of tests that fail because
>>>>>>> /var/lib/dbus/machine-id
>>>>>>> +is not present in the build environment.
>>>>>>
>>>>>> We usually work around these with:
>>>>>>
>>>>>> (setenv "DBUS_FATAL_WARNINGS" "0")
>>>>>>
>>>>>> Is it ineffective here?
>>>>>>
>>>>>
>>>>> That's good to know, but it doesn't seem to work in this case. I get 18
>>>>> test failures all from the same group mentioning the missing
>>>>> 'machine-id' file.
>>>>
>>>> Are they really errors and not just warnings (the errors being something
>>>> else)?
>>>>
>>>> Also, could it be that some Makefile or script forcefully sets
>>>> DBUS_FATAL_WARNINGS to 1, as is the case in ‘python-dbus’?
>>>>
>>>
>>> I see no such setting.
>>
>> OK. In that case your patch looks like the right thing to me.
>>
>> Thank you, and sorry for introducing more delay!
>>
>
> I'd rather be safe than sorry! Thanks for the review.
>
> Pushed to master as 85c774808fc13a0adc603784b2358a7c285c4822.
>
>> Ludo’.
Not sure if this is related, but I now get:
...
gcr-3.20.0/ui/gcr-prompt-dialog.c
gcr-3.20.0/README
patching file Makefile.in
Hunk #7 FAILED at 3268.
1 out of 10 hunks FAILED -- saving rejects to file Makefile.in.rej
source is under 'gcr-3.20.0'
applying
'/gnu/store/8dizfkad578r7n3iwafhmi9ckfnhx7lc-gcr-disable-failing-tests.patch'...
builder for `/gnu/store/b5p4nsrnsf55krjidq53mw93xcwbqzyb-gcr-3.20.0.tar.xz.drv'
failed to produce output path `/gnu/st
ore/ram3idajh7jwxk18k6ixaccgq0arigrx-gcr-3.20.0.tar.xz'
...
Does gcr build for you?
Kind regards,
Roel Janssen
- [bug#27542] [PATCH] gnu: gcr: Enable working tests., Ludovic Courtès, 2017/07/02
- [bug#27542] [PATCH] gnu: gcr: Enable working tests., Kei Kebreau, 2017/07/02
- [bug#27542] [PATCH] gnu: gcr: Enable working tests., Ludovic Courtès, 2017/07/02
- [bug#27542] [PATCH] gnu: gcr: Enable working tests., Kei Kebreau, 2017/07/02
- [bug#27542] [PATCH] gnu: gcr: Enable working tests., Ludovic Courtès, 2017/07/03
- bug#27542: [PATCH] gnu: gcr: Enable working tests., Kei Kebreau, 2017/07/03
- [bug#27542] [PATCH] gnu: gcr: Enable working tests.,
Roel Janssen <=
- [bug#27542] [PATCH] gnu: gcr: Enable working tests., Kei Kebreau, 2017/07/03
- [bug#27542] [PATCH] gnu: gcr: Enable working tests., Roel Janssen, 2017/07/04