Skip to content

OpenHarmony port: events #81

OpenHarmony port: events

OpenHarmony port: events #81

Triggered via push September 6, 2025 09:07
Status Success
Total duration 17m 6s
Artifacts –

build.yml

on: push
Create test plan
7s
Create test plan
Matrix: level1 / build
Matrix: level2 / build
Fit to window
Zoom out
Zoom in

Annotations

16 warnings and 12 notices
level2 / MacOS (GNU prefix)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
level2 / MacOS (GNU prefix)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
level2 / tvOS (CMake & xcode)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
level2 / tvOS (CMake & xcode)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
level2 / MacOS (Framework) (arm64)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
level2 / MacOS (Framework) (arm64)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
level2 / MacOS (Framework) (x64)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
level2 / MacOS (Framework) (x64)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
level2 / iOS (CMake & xcode)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
level2 / iOS (CMake & xcode)
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
level2 / Android (Android.mk)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0tfu7aAAAAABMH/mNsb+lTooNhfDW4ikhUEhYMzFFREdFMDYxNQBFZGdl
level2 / Android (Android.mk)
Failed to restore: Cache service responded with 400
level2 / Android (CMake, lean)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0ofu7aAAAAADgKdcK1y2tRpNsrWyPnH+YQkwyQUEyMDMwMTA4MDE3AEVkZ2U=
level2 / Android (CMake, lean)
Failed to restore: Cache service responded with 400
level2 / Android (CMake)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0g/u7aAAAAABMXCpxyi9NRLoYJ20tg5fHQkwyQUEyMDMwMTEwMDUxAEVkZ2U=
level2 / Android (CMake)
Failed to restore: Cache service responded with 400
level2 / Windows (MSVC, ARM64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / N-Gage
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (msys2, ucrt64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / GDK (MSVC, x64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (msys2, mingw64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (MSVC, clang-cl x86)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (MSVC, clang-cl x64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (MSVC, x86)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (MSVC, x64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (msys2, mingw32)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (MSVC, ARM)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
level2 / Windows (msys2, clang64)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677