Flent-users discussion archives
 help / color / mirror / Atom feed
From: ch <ch@ntrv.dk>
To: toke@toke.dk
Cc: flent-users@flent.org
Subject: [Flent-users] Re: bursts test does not complete (WAS: ERROR: Runner Burst 0 failed check: No command set for SilentProcessRunner)
Date: Thu, 30 Mar 2023 10:37:08 +0200	[thread overview]
Message-ID: <e8cc1925-b9ca-dd36-6744-2f996c956ae6@ntrv.dk> (raw)
In-Reply-To: <87zg7vmcnx.fsf@toke.dk>

On 30/03/2023 00.10, Toke Høiland-Jørgensen wrote:
>> I fell like I am getting more gray hairs by the hours. 🤕 I cannot
>> figure out why this happens.
>>
>> The burst test seems to run. Flent never "completes". Resulting in no
>> data output. :|
> It's crashing in the parsing step, leading to a hang; this is visible on
> stdout, so I guess your runner script hides that?

True. Switched to using systemd timers instead of crontab, saving logs 
from stdout/stderr going forwards. 💾 Had not initially thought about 
logging the output from the wrapper script. 🤦

> $ ./run-flent bursts -l 10
> Starting Flent 2.1.1+git.6959463f using Python 3.10.10.
> Starting bursts test. Expected run time: 10 seconds.
> Exception in thread Thread-8 (_handle_results):
> Traceback (most recent call last):
>    File "/usr/lib/python3.10/threading.py", line 1016, in _bootstrap_inner
>      self.run()
>    File "/usr/lib/python3.10/threading.py", line 953, in run
>      self._target(*self._args, **self._kwargs)
>    File "/usr/lib/python3.10/multiprocessing/pool.py", line 595, in _handle_results
>      cache[job]._set(i, obj)
>    File "/usr/lib/python3.10/multiprocessing/pool.py", line 779, in _set
>      self._callback(self._value)
>    File "/home/alrua/source/flent/flent/runners.py", line 625, in recv_result
>      result, raw_values, metadata = res
> TypeError: cannot unpack non-iterable NoneType object
> 
> Should be fixed in the latest master, please try that.

Installed the upgrade. 🤞

> Also, BTW, not sure what your wrapper script does, but Flent has a
> built-in batch run facility which may be helpful for such multi-run
> tests...

I wrote the wrapper script, due to not knowing about flent's batch 
capabilities initially. 🙄 Will look into the built-in batch 
capabilities instead of a wrapper script.

-ch


      reply	other threads:[~2023-03-30  8:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 12:20 [Flent-users] ERROR: Runner Burst 0 failed check: No command set for SilentProcessRunner Chriztoffer
2023-03-28 12:39 ` [Flent-users] " Toke Høiland-Jørgensen
2023-03-28 13:05   ` ch
2023-03-28 13:43     ` ch
2023-03-28 14:01       ` Toke Høiland-Jørgensen
2023-03-29  8:45         ` ch
2023-03-29 10:10           ` Toke Høiland-Jørgensen
2023-03-29 11:12             ` ch
2023-03-29 12:33               ` Toke Høiland-Jørgensen
2023-03-29 14:34                 ` ch
2023-03-29 17:42                   ` ch
2023-03-29 17:43                     ` ch
2023-03-29 19:48                       ` [Flent-users] Re: bursts test does not complete (WAS: ERROR: Runner Burst 0 failed check: No command set for SilentProcessRunner) ch
2023-03-29 22:10                         ` Toke Høiland-Jørgensen
2023-03-30  8:37                           ` ch [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

  List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e8cc1925-b9ca-dd36-6744-2f996c956ae6@ntrv.dk \
    --to=ch@ntrv.dk \
    --cc=flent-users@flent.org \
    --cc=toke@toke.dk \
    --subject='[Flent-users] Re: bursts test does not complete (WAS: ERROR: Runner Burst 0 failed check: No command set for SilentProcessRunner)' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox