Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
The full build log is available from:
http://qa-logs.debian.net/2025/03/27/crypto-equality-clojure_1.0.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250327;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250327&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

tag 1101600 + moreinfo
thanks

Hello,

As part of the build process, this package runs the upstream test suite,
which includes a test that does some timing measurements and checks if
they're within tolerances.

In this instance, the timings were slightly outside the predefined
threshold. I cannot reproduce this on my machine.

Is it possible that when this build was attempted, the system was under
a very heavy load? Eg. building very many packages simultaneously? If
so, it would explain this result.

I'm otherwise hesitant to remove or modify this particular unit test.

Thanks,

severity 1101600 normal
thanks

I'm downgrading the severity of this bug, as I've not been able to
reproduce it, and I believe the issue documented here is in all
likeliness the result of a degraded build environment suffering from
abnormally high resource contention.

Thanks,