helloadhavan/github_issues huggingface dataset:
Repository: ggml-org/llama.cpp
Pull request: fix(docker): add missing libglvnd libraries to Vulkan image

## Summary

Fixes #17761

Related: #16138

## Problem

The `mesa-vulkan-drivers` package has a runtime dependency on libglvnd libraries that aren't installed in the base image. Without them, the Mesa Vulkan ICD can't initialize properly and `vkEnumeratePhysicalDevices()` returns an empty device list, resulting in "ggml_vulkan: No devices found."

## Solution

Add the missing libglvnd libraries to `.devops/vulkan.Dockerfile`:

- libglvnd0
- libgl1
- libglx0
- libegl1
- libgles2

## Tests performed

- Dependencies check (`apt-get check`): OK, no conflicts
- Server starts correctly (`--help`, `--version`): OK
- Image size: 443MB -> 490MB (+47MB, +10.6%)
- llvmpipe software renderer: OK, no regressions

Before (original Dockerfile):
```
$ docker run --rm --device /dev/dri:/dev/dri llama-vulkan-original:test --list-devices
ggml_vulkan: No devices found.
```

After (with fix):
```
$ docker run --rm vulkan-test-fixed dpkg -l | grep -E 'libglvnd|libegl|libgl'
ii  libegl1:amd64         1.7.0-3    Vendor neutral GL dispatch library -- EGL support
ii  libgl1:amd64          1.7.0-3    Vendor neutral GL dispatch library -- legacy GL support
ii  libglvnd0:amd64       1.7.0-3    Vendor neutral GL dispatch library
ii  libglx0:amd64         1.7.0-3    Vendor neutral GL dispatch library -- GLX support
```

If anyone has additional tests they'd like to suggest, please let me know.

Changed files:
filename: .devops/vulkan.Dockerfile
patch: @@ -33,6 +33,7 @@ FROM ubuntu:$UBUNTU_VERSION AS base
 
 RUN apt-get update \
     && apt-get install -y libgomp1 curl libvulkan1 mesa-vulkan-drivers \
+    libglvnd0 libgl1 libglx0 libegl1 libgles2 \
     && apt autoremove -y \
     && apt clean -y \
     && rm -rf /tmp/* /var/tmp/* \
Repository: ggml-org/llama.cpp
Pull request: server : fix timing of prompt/generation

Measuring the time immediately after `llama_decode()` is incorrect for all asynchronous backends. We have been effectively incorrectly measuring the time of the last "prompt" batch as part of the  "generation" phase.

Might explain some unexpected timing reports recently when using `llama-server`.

Changed files:
filename: tools/server/server-context.cpp
patch: @@ -2615,10 +2615,6 @@ struct server_context_impl {
             // on successful decode, restore the original batch size
             n_batch = llama_n_batch(ctx);
 
-            // technically, measuring the time here excludes the sampling time for the last batch
-            // but on the other hand, we don't want to do too many system calls to measure the time, so it's ok
-            const int64_t t_current = ggml_time_us();
-
             for (auto & slot : slots) {
                 // may need to copy state to other slots
                 if (slot.state == SLOT_STATE_DONE_PROMPT && slot.is_parent()) {
@@ -2685,6 +2681,9 @@ struct server_context_impl {
 
                 common_sampler_accept(slot.smpl.get(), id, true);
 
+                // here we have synchronized the llama_context (due to the sampling above), so we can do time measurement
+                const int64_t t_current = ggml_time_us();
+
                 slot.n_decoded += 1;
 
                 if (slot.n_decoded == 1) {
@@ -2728,6 +2727,8 @@ struct server_context_impl {
                 slot.i_batch_dft.clear();
                 slot.drafted.clear();
 
+                const int64_t t_current = ggml_time_us();
+
                 slot.n_decoded += ids.size();
 
                 slot.t_token_generation = std::max<int64_t>(1, t_current - slot.t_start_generation) / 1e3;
Repository: nodejs/node
Pull request: test: ensure that the message event is fired

Use `common.mustCallAtLeast()` to verify that the `'message'` event is fired.

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: test/parallel/test-worker-message-port-infinite-message-loop.js
patch: @@ -11,7 +11,7 @@ const { MessageChannel } = require('worker_threads');
 
 const { port1, port2 } = new MessageChannel();
 let count = 0;
-port1.on('message', () => {
+port1.on('message', common.mustCallAtLeast(() => {
   if (count === 0) {
     setTimeout(common.mustCall(() => {
       port1.close();
@@ -20,7 +20,7 @@ port1.on('message', () => {
 
   port2.postMessage(0);
   assert(count++ < 10000, `hit ${count} loop iterations`);
-});
+}));
 
 port2.postMessage(0);
Repository: ollama/ollama
Pull request: Rocm v6 bump


Changed files:
filename: .github/workflows/test.yaml
patch: @@ -124,7 +124,7 @@ jobs:
     strategy:
       matrix:
         rocm-version:
-          - '6.0.2'
+          - '6.1.1'
     runs-on: linux
     container: rocm/dev-ubuntu-20.04:${{ matrix.rocm-version }}
     steps:

filename: Dockerfile
patch: @@ -2,7 +2,7 @@ ARG GOLANG_VERSION=1.22.1
 ARG CMAKE_VERSION=3.22.1
 # this CUDA_VERSION corresponds with the one specified in docs/gpu.md
 ARG CUDA_VERSION=11.3.1
-ARG ROCM_VERSION=6.0.2
+ARG ROCM_VERSION=6.1.1
 
 # Copy the minimal context we need to run the generate scripts
 FROM scratch AS llm-code
Repository: huggingface/transformers
Pull request: Fix the order of methods in processor loading

# What does this PR do?

As per title. The order was accidentally changed in prev PR and there's no reason for it. The reproducer is

```python
from transformers import Qwen2VLProcessor
import torch 

repo='hf-internal-testing/tiny-qwenimage-edit-pipe'
load_kwargs = {'subfolder': 'processor', 'variant': None, 'revision': None}
kwargs = {'torch_dtype': torch.float32}

processor = Qwen2VLProcessor.from_pretrained(repo, **load_kwargs, **kwargs)
```

Changed files:
filename: src/transformers/processing_utils.py
patch: @@ -1370,8 +1370,8 @@ def from_pretrained(
         if token is not None:
             kwargs["token"] = token
 
-        processor_dict, kwargs = cls.get_processor_dict(pretrained_model_name_or_path, **kwargs)
         args = cls._get_arguments_from_pretrained(pretrained_model_name_or_path, **kwargs)
+        processor_dict, kwargs = cls.get_processor_dict(pretrained_model_name_or_path, **kwargs)
         return cls.from_args_and_dict(args, processor_dict, **kwargs)
 
     @classmethod

filename: tests/models/auto/test_processor_auto.py
patch: @@ -88,6 +88,15 @@ def test_processor_from_local_directory_from_repo(self):
 
         self.assertIsInstance(processor, Wav2Vec2Processor)
 
+    def test_processor_from_local_subfolder_from_repo(self):
+        with tempfile.TemporaryDirectory() as tmpdirname:
+            processor = AutoProcessor.from_pretrained("facebook/wav2vec2-base-960h")
+            processor.save_pretrained(f"{tmpdirname}/processor_subfolder")
+
+            processor = Wav2Vec2Processor.from_pretrained(tmpdirname, subfolder="processor_subfolder")
+
+        self.assertIsInstance(processor, Wav2Vec2Processor)
+
     def test_processor_from_local_directory_from_extractor_config(self):
         with tempfile.TemporaryDirectory() as tmpdirname:
             # copy relevant files
Repository: ggml-org/llama.cpp
Pull request: scripts : pr2wt.sh reset to remote head

cont #18644 

Pull from latest remote.

Changed files:
filename: scripts/pr2wt.sh
patch: @@ -4,12 +4,13 @@
 #
 # - creates a new remote using the fork's clone URL
 # - creates a local branch tracking the remote branch
-# - creates a new worktree in a parent folder, suffixed with "-pr-${PR}"
+# - creates a new worktree in a parent folder, suffixed with "-pr-$PR"
 #
 # sample usage:
 #   ./scripts/pr2wt.sh 12345
 #   ./scripts/pr2wt.sh 12345 opencode
 #   ./scripts/pr2wt.sh 12345 "cmake -B build && cmake --build build"
+#   ./scripts/pr2wt.sh 12345 "bash -l"
 
 function usage() {
     echo "usage: $0 <pr_number> [cmd]"
@@ -39,29 +40,40 @@ org_repo=${org_repo%.git}
 
 echo "org/repo: $org_repo"
 
-meta=$(curl -sSf -H "Accept: application/vnd.github+json" "https://api.github.com/repos/${org_repo}/pulls/${PR}")
+meta=$(curl -sSf -H "Accept: application/vnd.github+json" "https://api.github.com/repos/$org_repo/pulls/$PR")
 
 url_remote=$(echo "$meta" | jq -r '.head.repo.clone_url')
 head_ref=$(echo "$meta" | jq -r '.head.ref')
 
 echo "url:      $url_remote"
 echo "head_ref: $head_ref"
 
-git remote rm  pr/${PR} 2> /dev/null
-git remote add pr/${PR} $url_remote
-git fetch      pr/${PR} $head_ref
+url_remote_cur=$(git config --get "remote.pr/$PR.url" 2>/dev/null || true)
+
+if [[ "$url_remote_cur" != "$url_remote" ]]; then
+    git remote rm  pr/$PR 2> /dev/null
+    git remote add pr/$PR "$url_remote"
+fi
+
+git fetch "pr/$PR" "$head_ref"
 
 dir=$(basename $(pwd))
 
 git branch -D pr/$PR 2> /dev/null
-git worktree add -b pr/$PR ../$dir-pr-$PR pr/$PR/${head_ref} 2> /dev/null
+git worktree add -b pr/$PR ../$dir-pr-$PR pr/$PR/$head_ref 2> /dev/null
 
 wt_path=$(cd ../$dir-pr-$PR && pwd)
 
 echo "git worktree created in $wt_path"
 
-# if a command was provided, execute it
+cd $wt_path
+git branch --set-upstream-to=pr/$PR/$head_ref
+git pull   --ff-only || {
+    echo "error: failed to pull pr/$PR"
+    exit 1
+}
+
 if [[ $# -eq 2 ]]; then
-    cd ../$dir-pr-$PR
+    echo "executing: $2"
     eval "$2"
 fi
Repository: electron/electron
Pull request: fix: fix and enable `accessibilitySupportEnabled` tests

#### Description of Change

Part 4 in a series to enable/fix tests that didn't run due to #46807. This one fixes the `accessibilitySupportEnabled` tests:

- Fix nested-it bug in the spec that prevented the tests from running.
- Fix tests that failed because they assumed the default initial state.
- Test every getter after calling each setter.

#### Checklist

- [x] PR description included and stakeholders cc'd
- [x] `npm test` passes
- [x] tests are [changed or added](https://github.com/electron/electron/blob/main/docs/development/testing.md)
- [x] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: none.

Changed files:
filename: spec/api-app-spec.ts
patch: @@ -979,22 +979,22 @@ describe('app module', () => {
   });
 
   ifdescribe(process.platform !== 'linux')('accessibilitySupportEnabled property', () => {
-    it('with properties', () => {
-      it('can set accessibility support enabled', () => {
-        expect(app.accessibilitySupportEnabled).to.eql(false);
-
-        app.accessibilitySupportEnabled = true;
-        expect(app.accessibilitySupportEnabled).to.eql(true);
-      });
-    });
-
-    describe('with functions', () => {
-      it('can set accessibility support enabled', () => {
-        expect(app.isAccessibilitySupportEnabled()).to.eql(false);
-
-        app.setAccessibilitySupportEnabled(true);
-        expect(app.isAccessibilitySupportEnabled()).to.eql(true);
-      });
+    it('is mutable', () => {
+      const values = [false, true, false];
+      const setters: Array<(arg: boolean) => void> = [
+        (value) => { app.accessibilitySupportEnabled = value; },
+        (value) => app.setAccessibilitySupportEnabled(value)
+      ];
+      const getters: Array<() => boolean> = [
+        () => app.accessibilitySupportEnabled,
+        () => app.isAccessibilitySupportEnabled()
+      ];
+      for (const value of values) {
+        for (const set of setters) {
+          set(value);
+          for (const get of getters) expect(get()).to.eql(value);
+        }
+      }
     });
   });
Repository: vercel/next.js
Pull request: Fix duplicate .next/types `include` on Windows

Closes https://github.com/vercel/next.js/pull/85056
Closes https://github.com/vercel/next.js/issues/85028
Closes https://linear.app/vercel/issue/NEXT-4754

## test plan

- [x] `pnpm create next-app && pnpm dev` does not alter the initial `tsconfig.json`

Changed files:
filename: packages/next/src/lib/typescript/writeConfigurationDefaults.ts
patch: @@ -1,4 +1,5 @@
 import { readFileSync, writeFileSync } from 'fs'
+import * as path from 'path'
 import { bold, cyan, white } from '../picocolors'
 import * as CommentJson from 'next/dist/compiled/comment-json'
 import semver from 'next/dist/compiled/semver'
@@ -267,7 +268,11 @@ export async function writeConfigurationDefaults(
     }
   }
 
-  const nextAppTypes: string[] = [`${distDir}/types/**/*.ts`]
+  const distDirPosix =
+    path.win32.sep === path.sep
+      ? distDir.replaceAll(path.win32.sep, path.posix.sep)
+      : distDir
+  const nextAppTypes: string[] = [`${distDirPosix}/types/**/*.ts`]
 
   // When isolatedDevBuild is enabled, Next.js uses different distDir paths:
   // - Development: "{distDir}/dev"
@@ -279,10 +284,10 @@ export async function writeConfigurationDefaults(
       process.env.NODE_ENV === 'development'
         ? // In dev, distDir is "{distDir}/dev", which is already in the array above, but we also need "{distDir}/types".
           // Here we remove "/dev" at the end of distDir for consistency.
-          `${distDir.replace(/\/dev$/, '')}/types/**/*.ts`
+          `${distDirPosix.replace(/\/dev$/, '')}/types/**/*.ts`
         : // In build, distDir is "{distDir}", which is already in the array above, but we also need "{distDir}/dev/types".
           // Here we add "/dev" at the end of distDir for consistency.
-          `${distDir}/dev/types/**/*.ts`
+          `${distDirPosix}/dev/types/**/*.ts`
     )
     // Sort the array to ensure consistent order.
     nextAppTypes.sort((a, b) => a.length - b.length)
Repository: facebook/react
Pull request: [react-compiler-runtime] Support React 17 peer dependency

<!--
  Thanks for submitting a pull request!
  We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

  Before submitting a pull request, please make sure the following is done:

  1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
  2. Run `yarn` in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
  5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
  6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect".
  7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
  8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
  9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
  10. If you haven't already, complete the CLA.

  Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->

## Summary

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->

The recent blog post and [documentation](https://react.dev/learn/react-compiler#using-react-compiler-with-react-17-or-18) say that `react-compiler-runtime` supports React 17, yet it currently requires React 18 or 19 as a peer dependency, making it unusable for installing on a project still using React 17.

## How did you test this change?

<!--
  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
  How exactly did you verify that your PR solves the issue you wanted to solve?
  If you leave this empty, your PR will very likely be closed.
-->

Manually installing the package on a React 17 codebase.

Changed files:
filename: compiler/packages/react-compiler-runtime/package.json
patch: @@ -9,7 +9,7 @@
     "src"
   ],
   "peerDependencies": {
-    "react": "^18.2.0 || ^19.0.0"
+    "react": "^17.0.0 || ^18.0.0 || ^19.0.0"
   },
   "scripts": {
     "build": "rimraf dist && rollup --config --bundleConfigAsCjs",
Repository: facebook/react
Pull request: [Flight] encodeURI filenames parsed from stack traces

When parsing stacks from third parties they may include invalid url characters. So we need to encode them. Since these are expected to be urls though we use just encodeURI instead of encodeURIComponent.


Changed files:
filename: packages/react-client/src/ReactFlightClient.js
patch: @@ -2275,12 +2275,12 @@ function createFakeFunction<T>(
       '\n//# sourceURL=rsc://React/' +
       encodeURIComponent(environmentName) +
       '/' +
-      filename +
+      encodeURI(filename) +
       '?' +
       fakeFunctionIdx++;
     code += '\n//# sourceMappingURL=' + sourceMap;
   } else if (filename) {
-    code += '\n//# sourceURL=' + filename;
+    code += '\n//# sourceURL=' + encodeURI(filename);
   } else {
     code += '\n//# sourceURL=<anonymous>';
   }

filename: packages/react-client/src/__tests__/ReactFlight-test.js
patch: @@ -1363,15 +1363,15 @@ describe('ReactFlight', () => {
             )
               ? expect.stringContaining(
                   'Error: This is an error\n' +
-                    '    at eval (eval at testFunction (eval at createFakeFunction (**), <anonymous>:1:35)\n' +
+                    '    at eval (eval at testFunction (inspected-page.html:29:11),%20%3Canonymous%3E:1:35)\n' +
                     '    at ServerComponentError (file://~/(some)(really)(exotic-directory)/ReactFlight-test.js:1166:19)\n' +
                     '    at <anonymous> (file:///testing.js:42:3)\n' +
                     '    at <anonymous> (file:///testing.js:42:3)\n' +
                     '    at div (<anonymous>',
                 )
               : expect.stringContaining(
                   'Error: This is an error\n' +
-                    '    at eval (eval at testFunction (inspected-page.html:29:11), <anonymous>:1:10)\n' +
+                    '    at eval (eval at testFunction (inspected-page.html:29:11),%20%3Canonymous%3E:1:10)\n' +
                     '    at ServerComponentError (file://~/(some)(really)(exotic-directory)/ReactFlight-test.js:1166:19)\n' +
                     '    at file:///testing.js:42:3\n' +
                     '    at file:///testing.js:42:3\n' +
Repository: ggml-org/llama.cpp
Pull request: ggml-webgpu: Fix GGML_MEM_ALIGN to 8 for emscripten.

Hello. When attempting to run LLM inference in the browser using WebGPU, the following error occurs.

<img width="534" height="83" alt="スクリーンショット 2026-01-06 0 31 03" src="https://github.com/user-attachments/assets/29d59388-9756-4135-a1f7-623ccef9e4a5" />

In Emscripten, `max_align_t` is 0x8(ref. https://github.com/emscripten-core/emscripten/issues/10072, https://github.com/emscripten-core/emscripten/pull/14599/files), which causes `GGML_ASSERT_ALIGNED` to fail.
Therefore, I modified the code to set `GGML_MEM_ALIGN` to 8 when running in an Emscripten environment.

I have confirmed that inference works correctly with `examples/simple-chat` for at least the following three models:
- Llama-3.2-1B-Instruct-Q4_1.gguf
- Llama-3.2-3B-Instruct-UD-Q4_K_XL.gguf
- Qwen3-4B-Thinking-2507-UD-IQ1_S.gguf

Changed files:
filename: ggml/include/ggml.h
patch: @@ -234,6 +234,11 @@
 
 #if UINTPTR_MAX == 0xFFFFFFFF
     #define GGML_MEM_ALIGN 4
+#elif defined(__EMSCRIPTEN__)
+// emscripten uses max_align_t == 8, so we need GGML_MEM_ALIGN == 8 for 64-bit wasm.
+// (for 32-bit wasm, the first conditional is true and GGML_MEM_ALIGN stays 4.)
+// ref: https://github.com/ggml-org/llama.cpp/pull/18628
+    #define GGML_MEM_ALIGN 8
 #else
     #define GGML_MEM_ALIGN 16
 #endif
Repository: ollama/ollama
Pull request: fix: "Skip searching for network devices"

On an Ubuntu 24.04 computer with vmware installed, the sudo lshw command will get stuck. "Network interfaces" is always displayed

Changed files:
filename: scripts/install.sh
patch: @@ -159,8 +159,8 @@ check_gpu() {
             esac ;;
         lshw)
             case $2 in
-                nvidia) available lshw && $SUDO lshw -c display -numeric | grep -q 'vendor: .* \[10DE\]' || return 1 ;;
-                amdgpu) available lshw && $SUDO lshw -c display -numeric | grep -q 'vendor: .* \[1002\]' || return 1 ;;
+                nvidia) available lshw && $SUDO lshw -c display -numeric -disable network | grep -q 'vendor: .* \[10DE\]' || return 1 ;;
+                amdgpu) available lshw && $SUDO lshw -c display -numeric -disable network | grep -q 'vendor: .* \[1002\]' || return 1 ;;
             esac ;;
         nvidia-smi) available nvidia-smi || return 1 ;;
     esac
Repository: electron/electron
Pull request: fix: fix and enable `accessibilitySupportEnabled` tests (36-x-y)

Manual backport of #46825 to 36-x-y. See that PR for details.

Notes: none.

Changed files:
filename: spec/api-app-spec.ts
patch: @@ -979,22 +979,22 @@ describe('app module', () => {
   });
 
   ifdescribe(process.platform !== 'linux')('accessibilitySupportEnabled property', () => {
-    it('with properties', () => {
-      it('can set accessibility support enabled', () => {
-        expect(app.accessibilitySupportEnabled).to.eql(false);
-
-        app.accessibilitySupportEnabled = true;
-        expect(app.accessibilitySupportEnabled).to.eql(true);
-      });
-    });
-
-    describe('with functions', () => {
-      it('can set accessibility support enabled', () => {
-        expect(app.isAccessibilitySupportEnabled()).to.eql(false);
-
-        app.setAccessibilitySupportEnabled(true);
-        expect(app.isAccessibilitySupportEnabled()).to.eql(true);
-      });
+    it('is mutable', () => {
+      const values = [false, true, false];
+      const setters: Array<(arg: boolean) => void> = [
+        (value) => { app.accessibilitySupportEnabled = value; },
+        (value) => app.setAccessibilitySupportEnabled(value)
+      ];
+      const getters: Array<() => boolean> = [
+        () => app.accessibilitySupportEnabled,
+        () => app.isAccessibilitySupportEnabled()
+      ];
+      for (const value of values) {
+        for (const set of setters) {
+          set(value);
+          for (const get of getters) expect(get()).to.eql(value);
+        }
+      }
     });
   });
Repository: huggingface/transformers
Pull request: Change trigger time for AMD CI

# What does this PR do?

docker build starts at 12AM. UTC+0. AMD docker file build in 4 hours. Let's trigger AMD CI at 5AM 

Changed files:
filename: .github/workflows/self-scheduled-amd-caller.yml
patch: @@ -2,7 +2,7 @@ name: Self-hosted runner (AMD scheduled CI caller)
 
 on:
   schedule:
-    - cron: "17 2 * * *"
+    - cron: "17 5 * * *"
 
 jobs:
   run_scheduled_amd_ci: