Hi,
For more context, see:
https://issues.guix.gnu.org/issue/31720
Because Debbugs sunset had been planed, I’m doing some janitor work and
I hit this very old ticket, last interaction 7 years, 38 weeks, 4 days
ago.
On Fri, 15 Jun 2018 at 13:29, Ricardo Wurmus <[email protected]> wrote:
>>> Le 2018-06-05 12:52, Ricardo Wurmus a écrit:
>>>> The package java-bouncycastle has a failing test suite on core-updates.
>>>> After the first test fails there is no more progress and the build
>>>> eventually times out.
>>>>
>>>> I have disabled the test suite for now, but we should try to fix this.
>>>>
>>>> The failing test is “org.bouncycastle.mail.smime.test.AllTests”.
>>>
>>> I've observed this behavior on master: the test fails, build hangs for
>>> some very long time and then resumes and completes. I'm not sure why
>>> there is a failure and how not to run this specific test though.
>>
>> Yes, you are right. The check phase does succeed after a very long
>> time.
>
> I think the bigger problem here is that we are running tests but
> silently ignore test failures. This happens since the change to ignore
> return values of build phases, because the ant-build-system only returns
> #f on a test failure when it should raise an exception instead.
Well, it’s still an issue, although last modified:
7de292e903b9fc6e9b13f1953182a6e4cf7fc74f
AuthorDate: Sun Dec 27 15:25:28 2020 +0100
CommitDate: Sun Dec 27 21:32:34 2020 +0100
gnu: java-bouncycastle: Update to 1.67.
* gnu/packages/java.scm (bouncycastle): Update to 1.67.
Somehow, I think that keeping this ticket open year after year does not
help in fixing it. Therefore, I propose to close it. And if we
consider it is still relevant, I propose to open a new ticket on
Codeberg <https://codeberg.org/guix/guix> for this issue will get the
attention it deserves.
WDYT?
Cheers,
simon
