[ci] [R-package] increase timeout on valgrind job

[jameslamb]

See #4391 (comment) and this failed job with a timeout of 180 minutes (https://github.com/microsoft/LightGBM/actions/runs/959047226).

It seems recently-added R package tests (or maybe some combination of that and changes in the C++ side) has led to the valgrind jobs exceeding 120 minutes. As a reminder, R runs substantially slower under valgrind (https://cran.r-project.org/doc/manuals/r-release/R-exts.html#Using-valgrind).

[jameslamb]

/gha run r-valgrind

Workflow R valgrind tests has been triggered! 🚀
https://github.com/microsoft/LightGBM/actions/runs/959283121

Status: failure ❌.

[jameslamb]

This job is failing with an error message that suggests that the job config is being sourced from master, not this branch.

The job running on runner GitHub Actions 125 has exceeded the maximum execution time of 120 minutes.

https://github.com/microsoft/LightGBM/actions/runs/959283121

(notice that it says "120 minutes")

@StrikerRUS , does that mean this needs to be merged to be tested?

[StrikerRUS]

@jameslamb

does that mean this needs to be merged to be tested?

Yes, you're right.

LightGBM/.github/workflows/r_valgrind.yml

Lines 3 to 5 in 4720889

	on:
	repository_dispatch:
	types: [gha_run_r_valgrind]

With repository_dispatch event trigger, workflow config is taken from the default branch (master in our case).
https://docs.github.com/en/actions/reference/events-that-trigger-workflows#repository_dispatch

[StrikerRUS]

Thank you.

[StrikerRUS]

Do you have rights to merge this PR with failing test?

[jameslamb]

It seems I don't have sufficient permissions to merge when a check is failing. Notice "squash and merge" is grayed out.

So I guess I'll have to open a new PR with these changes.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity since it was closed. To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues including a reference to this.