Let the inline test client say it is a local run, because it is one by wshlavacek · Pull Request #652 · lanl/PyBNF

wshlavacek · 2026-08-24T01:56:47Z

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so.

_report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the scheduler_info() call that claim leads to.

Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found.

Test only, one attribute. It just has to be present; nothing reads through it.

Checked on test_run_loop.py, test_wall_time_fit.py and test_cluster.py: 305 passed, 3 skipped, and the traceback is gone from a failing test's captured log.

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so. _report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the call that claim leads to. Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found. Test only. The attribute just has to be present; nothing reads through it.

wshlavacek · 2026-08-24T01:56:47Z

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so.

_report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the scheduler_info() call that claim leads to.

Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found.

Test only, one attribute. It just has to be present; nothing reads through it.

Checked on test_run_loop.py, test_wall_time_fit.py and test_cluster.py: 305 passed, 3 skipped, and the traceback is gone from a failing test's captured log.

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so. _report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the call that claim leads to. Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found. Test only. The attribute just has to be present; nothing reads through it.

wshlavacek · 2026-08-24T01:56:47Z

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so.

_report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the scheduler_info() call that claim leads to.

Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found.

Test only, one attribute. It just has to be present; nothing reads through it.

Checked on test_run_loop.py, test_wall_time_fit.py and test_cluster.py: 305 passed, 3 skipped, and the traceback is gone from a failing test's captured log.

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so. _report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the call that claim leads to. Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found. Test only. The attribute just has to be present; nothing reads through it.

wshlavacek · 2026-08-24T01:56:47Z

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so.

_report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the scheduler_info() call that claim leads to.

Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found.

Test only, one attribute. It just has to be present; nothing reads through it.

Checked on test_run_loop.py, test_wall_time_fit.py and test_cluster.py: 305 passed, 3 skipped, and the traceback is gone from a failing test's captured log.

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so. _report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the call that claim leads to. Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found. Test only. The attribute just has to be present; nothing reads through it.

wshlavacek · 2026-08-24T01:56:47Z

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so.

_report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the scheduler_info() call that claim leads to.

Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found.

Test only, one attribute. It just has to be present; nothing reads through it.

Checked on test_run_loop.py, test_wall_time_fit.py and test_cluster.py: 305 passed, 3 skipped, and the traceback is gone from a failing test's captured log.

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so. _report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the call that claim leads to. Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found. Test only. The attribute just has to be present; nothing reads through it.

wshlavacek · 2026-08-24T01:56:47Z

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so.

_report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the scheduler_info() call that claim leads to.

Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found.

Test only, one attribute. It just has to be present; nothing reads through it.

Checked on test_run_loop.py, test_wall_time_fit.py and test_cluster.py: 305 passed, 3 skipped, and the traceback is gone from a failing test's captured log.

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so. _report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the call that claim leads to. Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found. Test only. The attribute just has to be present; nothing reads through it.

wshlavacek · 2026-08-24T01:56:47Z

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so.

_report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the scheduler_info() call that claim leads to.

Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found.

Test only, one attribute. It just has to be present; nothing reads through it.

Checked on test_run_loop.py, test_wall_time_fit.py and test_cluster.py: 305 passed, 3 skipped, and the traceback is gone from a failing test's captured log.

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so. _report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the call that claim leads to. Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found. Test only. The attribute just has to be present; nothing reads through it.

wshlavacek · 2026-08-24T01:56:47Z

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so.

_report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the scheduler_info() call that claim leads to.

Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found.

Test only, one attribute. It just has to be present; nothing reads through it.

Checked on test_run_loop.py, test_wall_time_fit.py and test_cluster.py: 305 passed, 3 skipped, and the traceback is gone from a failing test's captured log.

FakeClient in the integration harness runs every submitted callable inline, so it stands in for a local run. It did not set the attribute that says so. _report_parallelism tells a local run from a cluster run by whether the client owns a cluster object, because a real local Client drives a LocalCluster and a cluster client connects to a scheduler and owns nothing. The double set no such attribute, so it presented itself as a cluster run, and then failed the call that claim leads to. Nothing breaks. The failure is caught and the fit is unaffected. What it costs is attention. The handler records a full traceback, and pytest shows a captured log only for a test that fails, so the traceback turns up in exactly the situation where someone is reading a log to find out why something broke, attached to a fit that broke for an unrelated reason. It came up while diagnosing #648 and had to be ruled out before the real cause could be found. Test only. The attribute just has to be present; nothing reads through it.