Merge branch 'master' into patch-1

Author: ffaahhimm

.github/actions/wait-for-check-completion/README.md

@@ -126,4 +126,4 @@ npm test
 
 ## Dependencies
 
-* Uses `caniuse-lite` sourced from [caniuse.com](caniuse.com)
+* Uses `caniuse-lite` sourced from [caniuse.com](https://caniuse.com)

.github/workflows/coverage.yml

@@ -104,7 +104,7 @@ jobs:
         continue-on-error: true
 
       # - name: Run Paddle frontend unit tests
-      #   run: ${{ github.workspace }}/bin/intel64/${{ env.CMAKE_BUILD_TYPE }}/paddle_tests --gtest_filter=-*IE_GPU*
+      #   run: ${{ github.workspace }}/bin/intel64/${{ env.CMAKE_BUILD_TYPE }}/ov_paddle_tests --gtest_filter=-*IE_GPU*
       #   continue-on-error: true
 
       - name: Run TensorFlow frontend unit tests

.github/workflows/job_cxx_unit_tests.yml

@@ -62,7 +62,7 @@ jobs:
         with:
           name: openvino_package
           path: ${{ env.INSTALL_DIR }}
-      
+
       - name: Download OpenVINO artifacts (tests)
         uses: actions/download-artifact@70fc10c6e5e1ce46ad2ea6f2b72d43f7d47b13c3 # v8.0.0
         with:
@@ -132,13 +132,13 @@ jobs:
         if: ${{ fromJSON(inputs.affected-components).PDPD_FE.test && runner.os != 'Windows' }} # Ticket: 149651
         run: |
           ${{ env.SOURCE_COMMAND }} ${{ env.SETUPVARS }}
-          ${{ env.INSTALL_TEST_DIR }}/paddle_tests --gtest_filter="-PaddleFuzzyOpTest*" --gtest_print_time=1 --gtest_output=xml:${{ env.INSTALL_TEST_DIR }}/TEST-PaddleTests.xml
+          ${{ env.INSTALL_TEST_DIR }}/ov_paddle_tests --gtest_filter="-PaddleFuzzyOpTest*" --gtest_print_time=1 --gtest_output=xml:${{ env.INSTALL_TEST_DIR }}/TEST-PaddleTests.xml
 
       - name: PaddlePaddle frontend Fuzzy Op tests
         if: ${{ inputs.event_name == 'schedule' && runner.os != 'Windows' }} # Ticket: 149651
         run: |
           ${{ env.SOURCE_COMMAND }} ${{ env.SETUPVARS }}
-          ${{ env.INSTALL_TEST_DIR }}/paddle_tests --gtest_filter="PaddleFuzzyOpTest*" --gtest_print_time=1 --gtest_output=xml:${{ env.INSTALL_TEST_DIR }}/TEST-PaddleFuzzyOpTests.xml
+          ${{ env.INSTALL_TEST_DIR }}/ov_paddle_tests --gtest_filter="PaddleFuzzyOpTest*" --gtest_print_time=1 --gtest_output=xml:${{ env.INSTALL_TEST_DIR }}/TEST-PaddleFuzzyOpTests.xml
 
       - name: ONNX frontend tests (GraphIterator default)
         if: ${{ fromJSON(inputs.affected-components).ONNX_FE.test && runner.arch != 'ARM64' }} # Ticket for macOS ARM64: 122663, for Linux ARM64: 126280, 153161
@@ -204,12 +204,12 @@ jobs:
           ${{ env.SOURCE_COMMAND }} ${{ env.SETUPVARS }}
           ${{ env.INSTALL_TEST_DIR }}/ov_cpu_unit_tests_vectorized --gtest_print_time=1 --gtest_output=xml:${{ env.INSTALL_TEST_DIR }}/TEST-CPUUnitTestsVectorized.xml
 
-      - name: NPU plugin unit tests 
+      - name: NPU plugin unit tests
         if: ${{fromJSON(inputs.affected-components).NPU.test && runner.os == 'Windows'}}
         run: |
           ${{ env.SOURCE_COMMAND }} ${{ env.SETUPVARS }}
           ${{ env.INSTALL_TEST_DIR }}/ov_npu_unit_tests --gtest_print_time=1 --gtest_output=xml:${{ env.INSTALL_TEST_DIR }}/TEST-NPUUnitTests.xml
-      
+
       - name: ov_subgraphs_dumper_tests tests
         run: |
           ${{ env.SOURCE_COMMAND }} ${{ env.SETUPVARS }}
@@ -256,7 +256,7 @@ jobs:
         run: |
           ${{ env.SOURCE_COMMAND }} ${{ env.SETUPVARS }}
           ${{ env.INSTALL_TEST_DIR }}/ov_auto_batch_unit_tests --gtest_output=xml:${{ env.INSTALL_TEST_DIR }}/TEST-ov_auto_batch_unit_tests.xml
-      
+
       # Disabled for debug build due to long execution time
       - name: AutoBatch func tests
         if: ${{ fromJSON(inputs.affected-components).AUTO_BATCH.test && inputs.build-type != 'debug' }}

.github/workflows/linux_sanitizers.yml

@@ -351,7 +351,7 @@ jobs:
         if: ${{ !cancelled() }}
         run: |
           source ${INSTALL_DIR}/setupvars.sh
-          ${INSTALL_TEST_DIR}/paddle_tests --gtest_print_time=1 \
+          ${INSTALL_TEST_DIR}/ov_paddle_tests --gtest_print_time=1 \
                 ${{ matrix.SANITIZER != '' && '--gtest_filter=-PaddleFuzzyOpTest/FrontEndFuzzyOpTest.testOpFuzzy/paddle_greater_equal_big_int64_greater_equal_big_int64_pdmodel' || '' }} \
                 --gtest_output=xml:${INSTALL_TEST_DIR}/TEST-PaddleTests.xml
 

docs/dev/build.md

@@ -21,7 +21,7 @@ The articles below provide the basic informations about the process of building
 * [Android](build_android.md)
 * [Raspbian Stretch](./build_raspbian.md)
 * [Web Assembly](./build_webassembly.md)
-* [Docker Image](https://github.com/openvinotoolkit/docker_ci/tree/master/dockerfiles/ubuntu18/build_custom)
+* [Docker Image](https://github.com/openvinotoolkit/docker_ci/tree/master/dockerfiles/ubuntu20/build_custom)
 * [Linux RISC-V](./build_riscv64.md)
 
 > **NOTE**: For the details on how to build static OpenVINO, refer to [Building static OpenVINO libraries](static_libaries.md)
@@ -31,4 +31,3 @@ The articles below provide the basic informations about the process of building
  * [OpenVINO README](../../README.md)
  * [OpenVINO Developer Documentation](index.md)
  * [OpenVINO Get Started](./get_started.md)
-

docs/dev/build_mac_intel_cpu.md

@@ -1,7 +1,7 @@
 # Build OpenVINO™ Runtime for macOS systems (Intel CPU)
 
 This guide shows how to build OpenVINO Runtime for later inference on Intel CPU on macOS with Intel CPU underneath. This can be done using two ways:
-- Compile on Intel CPU host using native compilation. Note, that [Build steps](#build-steps) show this scenario.
+- Compile on Intel CPU host using native compilation. Note, that [Build steps](#how-to-build) show this scenario.
 - Cross-compile on OSX Apple Silicon.
 
 The software was validated on:

docs/dev/building_documentation.md

@@ -5,8 +5,7 @@ The following procedure was validated on Windows and Ubuntu operation systems.
 ## Table of content:
 
 * [Installing dependencies](#installing-dependencies)
-* [Building documentation](#installing-dependencies)
-* [Additional Resources](#additional-resources)
+* [Building documentation](#building-documentation)
 
 ## Installing dependencies
 
@@ -15,7 +14,7 @@ The `doxygen` and `latex` must be installed in addition to usual build dependenc
 ### Windows
 
 * [miktex](https://miktex.org/)
-* [doxygen](http://doxygen.nl/files/doxygen-1.8.20-setup.exe) (version >= 1.8.20)
+* [doxygen](https://doxygen.nl/download.html) (version >= 1.8.20)
 * [Graphviz](https://graphviz.org/download/)
 
 ### Ubuntu systems

docs/dev/ci/github_actions/adding_tests.md

@@ -8,8 +8,8 @@ This document explains how to create new workflows and add tests.
 
 ## Table of Contents
 
-* [Adding Tests to an Existing Workflow](#adding-tests-to-existing-workflow)
-  * [Adding Tests to an Existing Test Suite](#adding-tests-to-existing-test-suite)
+* [Adding Tests to an Existing Workflow](#adding-tests-to-an-existing-workflow)
+  * [Adding Tests to an Existing Test Suite](#adding-tests-to-an-existing-test-suite)
   * [Creating a Step in a Job](#creating-a-step-in-a-job)
   * [Creating a New Job](#creating-a-new-job)
   * [Creating a Workflow](#creating-a-workflow)
@@ -118,7 +118,7 @@ A job:
 * requires a series of commands to execute, provided by the `steps` key
   * Refer to the [creating steps in a job section](#creating-a-step-in-a-job) to learn more about `steps`
 * might use build artifacts from the `Build` job
-  * The artifacts can be downloaded using `actions/download-artifact`, read more about the workflow structure in the [Overview of the OpenVINO GitHub Actions CI](./overview.md#structure-of-the-workflows)
+  * The artifacts can be downloaded using `actions/download-artifact`, read more about the workflow structure in the [Overview of the OpenVINO GitHub Actions CI](./overview.md#workflow-structure)
 
 If the job can be used in several workflows, it can be transformed into a reusable workflow.
 Learn more from the [Reusable Workflows page](./reusable_workflows.md).
@@ -128,7 +128,7 @@ Learn more from the [Reusable Workflows page](./reusable_workflows.md).
 To create a new workflow, add a new `<name>.yml` file to the [`.github/workflows`](./../../../../.github) folder.
 Refer to the [official GitHub Actions documentation](https://docs.github.com/en/actions/using-workflows/about-workflows#create-an-example-workflow) for a complete syntax reference, and browse the existing workflows in [`.github/workflows`](./../../../../.github).
 
-You can refer to the [structural overview of the existing workflows](./overview.md#structure-of-the-workflows) as a template for a new workflow.
+You can refer to the [structural overview of the existing workflows](./overview.md#workflow-structure) as a template for a new workflow.
 
 The [`fedora_29.yml`](./../../../../.github/workflows/fedora_29.yml) workflow example includes:
 * The following jobs:

docs/dev/ci/github_actions/caches.md

@@ -18,7 +18,7 @@ Three types of caches are available:
   * Accessible by `actions/cache` action.
   * Limited to 10 GB per repository.
   * Suitable for small dependencies caches and reusable artifacts.
-* [Shared drive cache](#shared-drive-cache-usage-and-structure)
+* [Shared drive cache](#shared-drive-cache)
   * Available only to self-hosted runners.
   * Automatically available via a predefined path.
   * Large storage.

docs/dev/ci/github_actions/overview.md

@@ -7,18 +7,17 @@ detailed instructions where necessary.
 ## Table of Contents
 
 * [Workflows overview](#workflows)
+  * [Reusing GitHub Actions](#reusing-github-actions)
   * [Triggers and schedules](#workflows-triggers-and-schedule)
-  * [Required workflows](#required-workflows)
-  * [Workflow structure](#structure-of-the-workflows)
-  * [Workflow and job organisation](#workflows-and-jobs-organisation)
+  * [Workflow structure](#workflow-structure)
   * [Security considerations](#security-considerations)
 * [Finding results, artifacts and logs](#finding-results-artifacts-and-logs)
 * [Custom actions overview](#custom-actions)
 * [Machines overview](#machines)
 * [Docker images overview](#docker-images)
 * [Caches overview](#caches)
 * [How to add new tests](#adding-new-tests)
-* [Optimizing workflow based on PR changes](#optimizing-workflow-based-on-PR-changes)
+* [Optimizing workflow based on PR changes](#optimizing-workflows-based-on-PR-changes)
 * [Merge Queue](#merge-queue)
 
 ## Workflows
@@ -32,18 +31,18 @@ They include:
 * information about the environment in which the commands should be executed
 
 
-You can find all workflows for this repository in the [workflows folder](../../../../.github/workflows).
+You can find all workflows for this repository in the [workflows folder](/.github/workflows).
 The three main ones, providing most coverage for different operating systems, are:
-* [Linux](../../../../.github/workflows/ubuntu_22.yml)
-* [Windows](../../../../.github/workflows/windows.yml)
-* [macOS](../../../../.github/workflows/mac.yml)
+* [Linux](/.github/workflows/ubuntu_22.yml)
+* [Windows](/.github/workflows/windows_vs2022_release.yml)
+* [macOS](/.github/workflows/mac_arm64.yml)
 
 Additionally, several supporting workflows build and test OpenVINO for other operating systems and processor architectures:
-* [Android](../../../../.github/workflows/android.yml)
-* [Fedora](../../../../.github/workflows/fedora_29.yml)
-* [Linux Conditional Compilation](../../../../.github/workflows/linux_conditional_compilation.yml)
-* [Linux RISC-V](../../../../.github/workflows/linux_riscv.yml)
-* [Windows Conditional Compilation](../../../../.github/workflows/windows_conditional_compilation.yml)
+* [Android](/.github/workflows/android.yml)
+* [Fedora](/.github/workflows/fedora_29.yml)
+* [Linux Conditional Compilation](/.github/workflows/linux_conditional_compilation.yml)
+* [Linux RISC-V](/.github/workflows/linux_riscv.yml)
+* [Windows Conditional Compilation](/.github/workflows/windows_conditional_compilation.yml)
 
 ### Reusing GitHub Actions
 
@@ -58,7 +57,7 @@ and see what and how to [obtain additional actions](https://github.com/marketpla
 Workflows run whenever they are triggered by predefined [events](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows).
 These triggers **are not** mutually exclusive and multiple can be used by one workflow.
 The OpenVINO repository has three, and as you may see in the example below, they are all
-included in the [Linux workflow](../../../../.github/workflows/ubuntu_22.yml). They are:
+included in the [Linux workflow](/.github/workflows/ubuntu_22.yml). They are:
 
 * `on: schedule` - schedule trigger
   * This trigger runs the workflow on a specified interval (e.g., nightly).
@@ -131,7 +130,7 @@ The workflow structures for Linux, Windows, and macOS are mostly the same:
 **NOTE**: some workflows may use the same structure, while others may lack the last 3 steps,
 with tests coming right after the `Build` step.
 
-Overview of the [Linux workflow](../../../../.github/workflows/ubuntu_22.yml).
+Overview of the [Linux workflow](/.github/workflows/ubuntu_22.yml).
 There are several jobs present:
 
 ```yaml
@@ -169,7 +168,7 @@ Each job has several keys that describe its environment. Consider checking a com
 
 This section describes the specifics of the OpenVINO CI environment.
 
-Overview of the [Linux workflow's](../../../../.github/workflows/ubuntu_22.yml) `Python_Unit_Tests` job:
+Overview of the [Linux workflow's](/.github/workflows/ubuntu_22.yml) `Python_Unit_Tests` job:
 ```yaml
   Python_Unit_Tests:
     name: Python unit tests