Hi,
Thanks for helping here.
On Fri, May 31, 2024 at 1:15 PM Thomas Friedrichsmeier
<thomas.friedrichsme...@kdemail.net> wrote:
>
> Hi,
>
> some first quick notes:
>
> This happens during running automated testing, and particularly while
> starting the backend process. The crash is probably not immediately to
> worry about, that used to be a bug when handling an already fatal
> condition.
>
> Looking at the tail of the log, where some debug output from the
> backend process is listed, things to seem to be going ok, but at a
> glacial speed (those numbers are timestamps in ms). The log terminates
> in the middle of the backend installing of one (the less important) of
> the two R support packages, without showing any error message.
>
> I'd have to check on the details of the test (core_test.cpp), but my
> first suspicion is that this is simply a timeout.
>
Yeah, Now Debian official buildd machines are still Unmatached[0]:
We have many timeout issues on Debian packages on riscv64
architectures. So I think we can increase timeout first to fix the
issue.
```
--- a/rkward/autotests/core_test.cpp
+++ b/rkward/autotests/core_test.cpp
@@ -57,7 +57,7 @@
class RKWardCoreTest: public QObject {
Q_OBJECT
- void runCommandWithTimeout(RCommand *command, RCommandChain*
chain, std::function<void(RCommand*)> callback, int timeoutms = 1000)
{
+ void runCommandWithTimeout(RCommand *command, RCommandChain*
chain, std::function<void(RCommand*)> callback, int timeoutms = 3000)
{
QString ccopy = command->command();
QElapsedTimer t;
t.start();
```
Just is it enough to modify here?
[0]: https://www.sifive.com/boards/hifive-unmatched
> Regards
> Thomas
