Nikita Titov
Nikita Titov
I'm +1 for @mayer79's proposal of documenting this problem.
Related: https://github.com/microsoft/LightGBM/pull/6539#issuecomment-2391779148
/AzurePipelines run
/AzurePipelines run
Kindly ping @jameslamb for this comment https://github.com/microsoft/LightGBM/pull/6832#discussion_r2059919981.
@davidfrickert Try to unset `HOME` env variable: https://github.com/nextcloud/docker/issues/2053#issuecomment-1676392064, https://github.com/nextcloud/docker/issues/2053#issuecomment-2422737735. This trick helped me.
Just got the same error code (104) in `master` but this time for `test_network_params_not_required_but_respected_if_given[scipy_csr_matrix-multiclass-classification]`: ``` 2021-03-21T13:41:14.1672682Z ============================= test session starts ============================== 2021-03-21T13:41:14.1674197Z platform linux -- Python 3.8.8, pytest-6.2.2, py-1.10.0, pluggy-0.13.1...
+2 failures with `104` error code today. It is getting frequent and annoying... **UPD:** +3 **UPD:** +4
I support `flaky` flag for Dask tests. But I'm afraid that it would enlarge CI time (due to extensive usage of `@pytest.mark.parametrize` we already have about 70 tests but only...
Hmm, quite strange that this error is progressing over time. Right now almost every PR and commit in `master` has to be re-run due to this error. I'm marking it...