The operation was canceled.
**Describe the bug** Since last week actions in our different repositories started to fail with similar error: #[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled. **To Reproduce** Steps to reproduce the behavior: 1. Go to Actions 2. Run or re-run any job 3. See error mentioned above **Expected behavior** Workflow should be running without cancellations. ## Runner Version and Platform Image: ubuntu-22.04 Version: 20230219.1 Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20230219.1/images/linux/Ubuntu2204-Readme.md Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20230219.1 OS of the machine running the runner? Linux ## What's not working? Workflow is failing without any reason stated in the logs, apart from it has been cancelled. ## Job Log Output 2023-03-01T06:49:56.3959504Z > @mgnation/mgdata@1.4.212 _bundle 2023-03-01T06:49:56.3960408Z > node build/bundle.js 2023-03-01T06:49:56.3960710Z 2023-03-01T06:49:56.8884234Z [32mBundling has started[0m 2023-03-01T06:49:56.9282005Z [34mCopy results completed[0m 2023-03-01T06:49:56.9290747Z [34mAllow publish completed[0m 2023-03-01T06:49:56.9295155Z build: 39.141ms 2023-03-01T06:49:56.9302039Z [32mBundling has finished[0m 2023-03-01T06:49:57.2702808Z 2023-03-01T06:49:57.2708891Z > @mgnation/mgdata@1.4.212 test 2023-03-01T06:49:57.2709823Z > node ./node_modules/nyc/bin/ny
Posted by magnetnation on Mar 1, 2023, 7:01 AM
Tags
Related issues
- Many devs love to shit on the guy from the 'I just want the exe.
- Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
- Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
- I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
- Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
- I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
reliability (SaaS)
Many devs love to shit on the guy from the 'I just want the exe.
Now imagine how poor people stress if their smartphone bricks or gets damaged or lost.
Resuming an extended-thinking session fails permanently with 400 "thinking blocks cannot be modified" (transcript stores thinking text as empty but keeps signat
I'll preface this with a statement that as a European I want European alternatives to succeed, and MS-owned GitHub to shrivel and disappear.
Yeah, but there’s a world of difference between “not perfect” and “we rounded a few sliders, and now the modal is a nightmare to use”.
I used to write a lot of native Windows corporate software in the 90's and 2000's and my standard login window was a floating draggable o...
App broken with Mosquitto broker 7.0.0
[BUG] Remote Control: automatic reconnection doesn't work -- connection drops silently with no recovery
The operation was canceled.
**Describe the bug** Since last week actions in our different repositories started to fail with similar error: #[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled. **To Reproduce** Steps to reproduce the behavior: 1. Go to Actions 2. Run or re-run any job 3. See error mentioned above **Expected behavior** Workflow should be running without cancellations. ## Runner Version and Platform Image: ubuntu-22.04 Version: 20230219.1 Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20230219.1/images/linux/Ubuntu2204-Readme.md Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20230219.1 OS of the machine running the runner? Linux ## What's not working? Workflow is failing without any reason stated in the logs, apart from it has been cancelled. ## Job Log Output 2023-03-01T06:49:56.3959504Z > @mgnation/mgdata@1.4.212 _bundle 2023-03-01T06:49:56.3960408Z > node build/bundle.js 2023-03-01T06:49:56.3960710Z 2023-03-01T06:49:56.8884234Z [32mBundling has started[0m 2023-03-01T06:49:56.9282005Z [34mCopy results completed[0m 2023-03-01T06:49:56.9290747Z [34mAllow publish completed[0m 2023-03-01T06:49:56.9295155Z build: 39.141ms 2023-03-01T06:49:56.9302039Z [32mBundling has finished[0m 2023-03-01T06:49:57.2702808Z 2023-03-01T06:49:57.2708891Z > @mgnation/mgdata@1.4.212 test 2023-03-01T06:49:57.2709823Z > node ./node_modules/nyc/bin/ny
Comments (0)
No comments yet. Start the discussion.