Skip to content

fix the embedded null character issue #1995

fix the embedded null character issue

fix the embedded null character issue #1995

Triggered via pull request July 14, 2025 14:29
Status Failure
Total duration 11m 11s
Artifacts 7

test-and-publish.yaml

on: pull_request
Matrix: build-spidermonkey-unix
build-spidermonkey-win
26s
build-spidermonkey-win
Matrix: build-and-test
publish
publish
publish-archive
publish-archive
publish-nightly
publish-nightly
Fit to window
Zoom out
Zoom in

Annotations

85 errors and 36 warnings
build-and-test (macos-14, 3.13)
Process completed with exit code 1.
build-and-test (macos-14, 3.13)
Process completed with exit code 1.
build-and-test (macos-14, 3.13)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (macos-14, 3.10)
Process completed with exit code 1.
build-and-test (macos-14, 3.10)
Process completed with exit code 1.
build-and-test (macos-14, 3.10)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (macos-14, 3.9)
Process completed with exit code 1.
build-and-test (macos-14, 3.9)
Process completed with exit code 1.
build-and-test (macos-14, 3.9)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (ubuntu-22.04-arm, 3.9)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.9)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.12)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.12)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.10)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.10)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.11)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.11)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.10)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.10)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.10)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.10)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build-and-test (ubuntu-22.04, 3.11)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.11)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.11)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.11)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build-and-test (macos-13, 3.9)
Process completed with exit code 1.
build-and-test (macos-13, 3.9)
Process completed with exit code 1.
build-and-test (macos-13, 3.9)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (ubuntu-22.04, 3.13)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.13)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.13)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.13)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
build-and-test (ubuntu-22.04-arm, 3.13)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.13)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.8)
Process completed with exit code 1.
build-and-test (ubuntu-22.04-arm, 3.8)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.8)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.8)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.8)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.8)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build-and-test (windows-2022, 3.10)
Process completed with exit code 1.
build-and-test (windows-2022, 3.10)
Process completed with exit code 1.
build-and-test (windows-2022, 3.12)
Process completed with exit code 1.
build-and-test (windows-2022, 3.12)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.9)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.9)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.9)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.9)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
build-and-test (windows-2022, 3.11)
Process completed with exit code 1.
build-and-test (windows-2022, 3.11)
Process completed with exit code 1.
build-and-test (windows-2022, 3.13)
Process completed with exit code 1.
build-and-test (windows-2022, 3.13)
Process completed with exit code 1.
build-and-test (macos-13, 3.11)
Process completed with exit code 1.
build-and-test (macos-13, 3.11)
Process completed with exit code 1.
build-and-test (macos-13, 3.11)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (windows-2022, 3.8)
Process completed with exit code 1.
build-and-test (windows-2022, 3.8)
Process completed with exit code 1.
build-and-test (macos-13, 3.10)
Process completed with exit code 1.
build-and-test (macos-13, 3.10)
Process completed with exit code 1.
build-and-test (macos-13, 3.10)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (macos-14, 3.8)
Process completed with exit code 1.
build-and-test (macos-14, 3.8)
Process completed with exit code 1.
build-and-test (macos-14, 3.8)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (macos-14, 3.8)
[notice] A new release of pip is available: 21.1.1 -> 25.0.1 [notice] To update, run: python3.8 -m pip install --upgrade pip
build-and-test (macos-13, 3.13)
Process completed with exit code 1.
build-and-test (macos-13, 3.13)
Process completed with exit code 1.
build-and-test (macos-13, 3.13)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (windows-2022, 3.9)
Process completed with exit code 1.
build-and-test (windows-2022, 3.9)
Process completed with exit code 1.
build-and-test (macos-14, 3.11)
Process completed with exit code 1.
build-and-test (macos-14, 3.11)
Process completed with exit code 1.
build-and-test (macos-14, 3.11)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (ubuntu-22.04, 3.12)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.12)
Process completed with exit code 1.
build-and-test (ubuntu-22.04, 3.12)
WARNING: The directory '/github/home/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
build-and-test (ubuntu-22.04, 3.12)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
build-and-test (macos-14, 3.12)
Process completed with exit code 1.
build-and-test (macos-14, 3.12)
Process completed with exit code 1.
build-and-test (macos-14, 3.12)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (macos-13, 3.12)
Process completed with exit code 1.
build-and-test (macos-13, 3.12)
Process completed with exit code 1.
build-and-test (macos-13, 3.12)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (macos-13, 3.8)
Process completed with exit code 1.
build-and-test (macos-13, 3.8)
Process completed with exit code 1.
build-and-test (macos-13, 3.8)
cmake 3.31.6 is already installed To upgrade to 4.0.3, run: brew upgrade cmake
build-and-test (macos-14, 3.13)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.13)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-14, 3.13)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-14, 3.10)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.10)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-14, 3.10)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-14, 3.9)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.9)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-14, 3.9)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-13, 3.9)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.9)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.9)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-13, 3.11)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.11)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.11)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-13, 3.10)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.10)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.10)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-14, 3.8)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.8)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-14, 3.8)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-13, 3.13)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.13)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.13)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-14, 3.11)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.11)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-14, 3.11)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-14, 3.12)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-14, 3.12)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-14, 3.12)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-13, 3.12)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.12)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.12)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
build-and-test (macos-13, 3.8)
HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK is set: not checking for outdated dependents or dependents with broken linkage!
build-and-test (macos-13, 3.8)
wget 1.25.0 is already installed and up-to-date. To reinstall 1.25.0, run: brew reinstall wget
build-and-test (macos-13, 3.8)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf

Artifacts

Produced during runtime
Name Size Digest
docs-16269641669-d800e4aead7a219c81d759e38d2d95f6e9884746 Expired
2.81 MB
sha256:399fd04491cec1ef845d0ad5be4355356915cc77eb0f2fbc0c2140399947e00a
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-Linux-ARM64 Expired
51.9 MB
sha256:76e031a40c5aeb1e495507073457c043ca5d10f123ba100a6603dbe6737a7c7f
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-Linux-X64 Expired
52.4 MB
sha256:32f7e5ceed3d4ade19ef15f316412a7ee42b98c4d93b3e2a18f1dc9ef4d68057
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-Windows-X64 Expired
30.3 MB
sha256:d63e07011f604ee826fe8a8d98d599135c4679b48492c93ddbd791c1e88d97e7
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-macOS-ARM64 Expired
45.8 MB
sha256:86539e0be1fb29f84688ed9239c4a2aa85c2278baa7fd093d3d06f0da7f2cda7
spidermonkey-6bca861985ba51920c1cacc21986af01c51bd690-macOS-X64 Expired
46.6 MB
sha256:f5e8981ab0ecfc6f6c6a86833e5e1c6bc184c000f4083fd1f8706b221050d772
wheel-16269641669-d800e4aead7a219c81d759e38d2d95f6e9884746-sdist Expired
302 KB
sha256:964de4e2272c4cce666b7ff76033630ae708babd709687fb8f19ffb21b19dcab