[fully_async] fix: replace routed_experts on partial rollout resume i… #6029
Annotations
6 errors and 1 warning
|
Post Checkout verl-project/verl repo
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Post Checkout verl-project/verl repo
Process completed with exit code 1.
|
|
Post Checkout verl-project/verl repo
Error: failed to run script step: Error: Internal error occurred: unable to upgrade connection: container not found ("job")
|
|
Running GSM8K E2E training tests on 8 L20 GPUs with rmpad using function rm with validation and saving (FSDP2)
Executing the custom container implementation failed. Please contact your self hosted runner administrator.
|
|
Running GSM8K E2E training tests on 8 L20 GPUs with rmpad using function rm with validation and saving (FSDP2)
Process completed with exit code 1.
|
|
Running GSM8K E2E training tests on 8 L20 GPUs with rmpad using function rm with validation and saving (FSDP2)
Error: failed to run script step: Error: command terminated with non-zero exit code: command terminated with exit code 137
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Loading