Exception calling "SetPageFileSize" with "3" argument(s): "The operation completed successfully" At D:\a\_actions\al-cheb\configure-pagefile-action\v1.3\scripts\SetPageFileSize.ps1:193 char:1 + [Util.PageFile]::SetPageFileSize($minimumSize, $maximumSize, $diskRoo ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [], MethodInvocationException + FullyQualifiedErrorId : Win32Exception

3.7 Windows / compile (windows, windows-cl, win_amd64, C:/cpp_build, C:/vcpkg_packages, *.pdb, *.lib, *.ilk, *....

3.10 Windows / compile (windows, windows-cl, win_amd64, C:/cpp_build, C:/vcpkg_packages, *.pdb, *.lib, *.ilk, *....

3.11 Windows / compile (windows, windows-cl, win_amd64, C:/cpp_build, C:/vcpkg_packages, *.pdb, *.lib, *.ilk, *....

3.9 Windows / compile (windows, windows-cl, win_amd64, C:/cpp_build, C:/vcpkg_packages, *.pdb, *.lib, *.ilk, *....

3.8 Windows / compat

3.7 Windows / compat

3.11 Windows / compat

3.10 Windows / compat

3.9 Windows / compat

Windows C++ Tests / compile (windows, windows-cl, win_amd64, C:/cpp_build, C:/vcpkg_packages, *.pdb, *.lib, *.ilk, *....

3.10 Windows / stress

3.7 Windows / stress

3.11 Windows / stress

3.8 Windows / stress

3.9 Windows / stress

3.7 Linux / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 141 has exceeded the maximum execution time of 360 minutes.

3.7 Linux / {hypothesis,nonreg,scripts}

The operation was canceled.

3.7 Linux / unit

The job running on runner GitHub Actions 27 has exceeded the maximum execution time of 360 minutes.

3.7 Linux / unit

The operation was canceled.

3.7 Linux / integration

The job running on runner GitHub Actions 345 has exceeded the maximum execution time of 360 minutes.

3.7 Linux / integration

The operation was canceled.

3.8 Linux / unit

The job running on runner GitHub Actions 70 has exceeded the maximum execution time of 360 minutes.

3.8 Linux / unit

The operation was canceled.

3.8 Linux / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 152 has exceeded the maximum execution time of 360 minutes.

3.8 Linux / {hypothesis,nonreg,scripts}

The operation was canceled.

3.8 Linux / {hypothesis,nonreg,scripts}-compat38

The job running on runner GitHub Actions 215 has exceeded the maximum execution time of 360 minutes.

3.8 Linux / {hypothesis,nonreg,scripts}-compat38

The operation was canceled.

3.8 Linux / integration-compat38

The job running on runner GitHub Actions 90 has exceeded the maximum execution time of 360 minutes.

3.8 Linux / integration-compat38

The operation was canceled.

3.8 Linux / integration

The job running on runner GitHub Actions 289 has exceeded the maximum execution time of 360 minutes.

3.8 Linux / integration

The operation was canceled.

3.8 Linux / unit-compat38

The job running on runner GitHub Actions 1 has exceeded the maximum execution time of 360 minutes.

3.8 Linux / unit-compat38

The operation was canceled.

3.6 Linux / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 41 has exceeded the maximum execution time of 360 minutes.

3.6 Linux / {hypothesis,nonreg,scripts}

The operation was canceled.

3.6 Linux / {hypothesis,nonreg,scripts}-compat36

The job running on runner GitHub Actions 172 has exceeded the maximum execution time of 360 minutes.

3.6 Linux / {hypothesis,nonreg,scripts}-compat36

The operation was canceled.

3.6 Linux / unit

The job running on runner GitHub Actions 206 has exceeded the maximum execution time of 360 minutes.

3.6 Linux / unit

The operation was canceled.

3.6 Linux / integration-compat36

The job running on runner GitHub Actions 44 has exceeded the maximum execution time of 360 minutes.

3.6 Linux / integration-compat36

The operation was canceled.

3.6 Linux / unit-compat36

The job running on runner GitHub Actions 382 has exceeded the maximum execution time of 360 minutes.

3.6 Linux / unit-compat36

The operation was canceled.

3.6 Linux / integration

The job running on runner GitHub Actions 36 has exceeded the maximum execution time of 360 minutes.

3.6 Linux / integration

The operation was canceled.

3.8 Windows / unit

The job running on runner GitHub Actions 195 has exceeded the maximum execution time of 360 minutes.

3.8 Windows / unit

The operation was canceled.

3.8 Windows / unit

3.8 Windows / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 129 has exceeded the maximum execution time of 360 minutes.

3.8 Windows / {hypothesis,nonreg,scripts}

The operation was canceled.

3.8 Windows / {hypothesis,nonreg,scripts}

3.8 Windows / integration

The job running on runner GitHub Actions 337 has exceeded the maximum execution time of 360 minutes.

3.8 Windows / integration

The operation was canceled.

3.7 Windows / integration

The job running on runner GitHub Actions 55 has exceeded the maximum execution time of 360 minutes.

3.7 Windows / integration

The operation was canceled.

3.7 Windows / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 91 has exceeded the maximum execution time of 360 minutes.

3.7 Windows / {hypothesis,nonreg,scripts}

The operation was canceled.

3.7 Windows / unit

The job running on runner GitHub Actions 94 has exceeded the maximum execution time of 360 minutes.

3.7 Windows / unit

The operation was canceled.

3.11 Linux / unit

The job running on runner GitHub Actions 324 has exceeded the maximum execution time of 360 minutes.

3.11 Linux / unit

The operation was canceled.

3.11 Linux / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 31 has exceeded the maximum execution time of 360 minutes.

3.11 Linux / {hypothesis,nonreg,scripts}

The operation was canceled.

3.11 Linux / integration

The job running on runner GitHub Actions 3 has exceeded the maximum execution time of 360 minutes.

3.11 Linux / integration

The operation was canceled.

3.10 Windows / integration

The job running on runner GitHub Actions 37 has exceeded the maximum execution time of 360 minutes.

3.10 Windows / integration

The operation was canceled.

3.10 Windows / integration

3.10 Windows / unit

The job running on runner GitHub Actions 437 has exceeded the maximum execution time of 360 minutes.

3.10 Windows / unit

The operation was canceled.

3.10 Windows / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 211 has exceeded the maximum execution time of 360 minutes.

3.10 Windows / {hypothesis,nonreg,scripts}

The operation was canceled.

3.11 Windows / integration

The job running on runner GitHub Actions 459 has exceeded the maximum execution time of 360 minutes.

3.11 Windows / integration

The operation was canceled.

3.11 Windows / integration

3.11 Windows / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 169 has exceeded the maximum execution time of 360 minutes.

3.11 Windows / {hypothesis,nonreg,scripts}

The operation was canceled.

3.11 Windows / {hypothesis,nonreg,scripts}

3.11 Windows / unit

The job running on runner GitHub Actions 165 has exceeded the maximum execution time of 360 minutes.

3.11 Windows / unit

The operation was canceled.

3.9 Windows / unit

The job running on runner GitHub Actions 499 has exceeded the maximum execution time of 360 minutes.

3.9 Windows / unit

The operation was canceled.

3.9 Windows / unit

3.9 Windows / integration

The job running on runner GitHub Actions 109 has exceeded the maximum execution time of 360 minutes.

3.9 Windows / integration

The operation was canceled.

3.9 Windows / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 402 has exceeded the maximum execution time of 360 minutes.

3.9 Windows / {hypothesis,nonreg,scripts}

The operation was canceled.

3.9 Windows / {hypothesis,nonreg,scripts}

3.9 Linux / unit

The job running on runner GitHub Actions 151 has exceeded the maximum execution time of 360 minutes.

3.9 Linux / unit

The operation was canceled.

3.9 Linux / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 333 has exceeded the maximum execution time of 360 minutes.

3.9 Linux / {hypothesis,nonreg,scripts}

The operation was canceled.

3.9 Linux / integration

The job running on runner GitHub Actions 301 has exceeded the maximum execution time of 360 minutes.

3.9 Linux / integration

The operation was canceled.

3.10 Linux / {hypothesis,nonreg,scripts}

The job running on runner GitHub Actions 259 has exceeded the maximum execution time of 360 minutes.

3.10 Linux / {hypothesis,nonreg,scripts}

The operation was canceled.

3.10 Linux / unit

The job running on runner GitHub Actions 185 has exceeded the maximum execution time of 360 minutes.

3.10 Linux / unit

The operation was canceled.

3.10 Linux / integration

The job running on runner GitHub Actions 190 has exceeded the maximum execution time of 360 minutes.

3.10 Linux / integration

The operation was canceled.

cibw_docker_image / work

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

3.7 Linux / compat

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / compat

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / compat-compat38

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.11 Linux / compat

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.9 Linux / compat

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.10 Linux / compat

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

Windows C++ Tests / compile (windows, windows-cl, win_amd64, C:/cpp_build, C:/vcpkg_packages, *.pdb, *.lib, *.ilk, *....

Skipping setting up the environment since vcpkg's executable is not found at: 'D:�\ArcticDB\ArcticDBCMAKE_BUILD_PARALLEL_LEVEL=4\vcpkg.exe'.

Windows C++ Tests / compile (windows, windows-cl, win_amd64, C:/cpp_build, C:/vcpkg_packages, *.pdb, *.lib, *.ilk, *....: cpp/third_party/lmdbcxx/mdb.c#L7444

'>>': right shift by too large amount, data loss

Windows C++ Tests / compile (windows, windows-cl, win_amd64, C:/cpp_build, C:/vcpkg_packages, *.pdb, *.lib, *.ilk, *....: cpp/third_party/lmdbcxx/mdb.c#L1515

returning address of local variable or temporary : buf

3.8 Linux / stress-compat38

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.7 Linux / stress

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / stress

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.11 Linux / stress

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.6 Linux / stress

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.6 Linux / stress-compat36

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.10 Linux / stress

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.9 Linux / stress

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

The following variables are not used in CMakeLists.txt:

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

vcpkg_replace_string made no changes.

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

The following variables are not used in CMakeLists.txt:

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

vcpkg_replace_string made no changes.

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

vcpkg_replace_string made no changes.

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

vcpkg_replace_string made no changes.

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

vcpkg_replace_string made no changes.

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

variable ‘rc’ set but not used [-Wunused-but-set-variable]

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

this statement may fall through [-Wimplicit-fallthrough=]

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

writing 8 bytes into a region of size 1 [-Wstringop-overflow=]

Linux C++ Tests / compile (linux, linux, manylinux_x86_64, /tmp/cpp_build, *.gz, *.so, *.[ao], vcpkg_installed, mon...

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.7 Linux / {hypothesis,nonreg,scripts}

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.7 Linux / unit

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.7 Linux / integration

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / unit

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / {hypothesis,nonreg,scripts}

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / {hypothesis,nonreg,scripts}-compat38

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / integration-compat38

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / integration

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.8 Linux / unit-compat38

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.6 Linux / {hypothesis,nonreg,scripts}

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.6 Linux / {hypothesis,nonreg,scripts}-compat36

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.6 Linux / unit

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.6 Linux / integration-compat36

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.6 Linux / unit-compat36

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.6 Linux / integration

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.11 Linux / unit

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.11 Linux / {hypothesis,nonreg,scripts}

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.11 Linux / integration

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.9 Linux / unit

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.9 Linux / {hypothesis,nonreg,scripts}

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.9 Linux / integration

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.10 Linux / {hypothesis,nonreg,scripts}

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.10 Linux / unit

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

3.10 Linux / integration

Volume mount /:/mnt is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

Deprecation notice: v1, v2, and v3 of the artifact actions

The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "build-metadata-build-python-wheels-linux-cp310", "build-metadata-build-python-wheels-linux-cp311", "build-metadata-build-python-wheels-linux-cp36", "build-metadata-build-python-wheels-linux-cp37", "build-metadata-build-python-wheels-linux-cp38", "build-metadata-build-python-wheels-linux-cp39", "build-metadata-build-python-wheels-windows-cp310", "build-metadata-build-python-wheels-windows-cp311", "build-metadata-build-python-wheels-windows-cp37", "build-metadata-build-python-wheels-windows-cp38", "build-metadata-build-python-wheels-windows-cp39", "build-metadata-cpp-tests-linux-default", "build-metadata-cpp-tests-windows-default", "pytest-linux-cp310-{hypothesis,nonreg,scripts}", "pytest-linux-cp310-compat", "pytest-linux-cp310-integration", "pytest-linux-cp310-stress", "pytest-linux-cp310-unit", "pytest-linux-cp311-{hypothesis,nonreg,scripts}", "pytest-linux-cp311-compat", "pytest-linux-cp311-integration", "pytest-linux-cp311-stress", "pytest-linux-cp311-unit", "pytest-linux-cp36-{hypothesis,nonreg,scripts}", "pytest-linux-cp36-{hypothesis,nonreg,scripts}-compat36", "pytest-linux-cp36-integration", "pytest-linux-cp36-integration-compat36", "pytest-linux-cp36-stress", "pytest-linux-cp36-stress-compat36", "pytest-linux-cp36-unit", "pytest-linux-cp36-unit-compat36", "pytest-linux-cp37-{hypothesis,nonreg,scripts}", "pytest-linux-cp37-compat", "pytest-linux-cp37-integration", "pytest-linux-cp37-stress", "pytest-linux-cp37-unit", "pytest-linux-cp38-{hypothesis,nonreg,scripts}", "pytest-linux-cp38-{hypothesis,nonreg,scripts}-compat38", "pytest-linux-cp38-compat", "pytest-linux-cp38-compat-compat38", "pytest-linux-cp38-integration", "pytest-linux-cp38-integration-compat38", "pytest-linux-cp38-stress", "pytest-linux-cp38-stress-compat38", "pytest-linux-cp38-unit", "pytest-linux-cp38-unit-compat38", "pytest-linux-cp39-{hypothesis,nonreg,scripts}", "pytest-linux-cp39-compat", "pytest-linux-cp39-integration", "pytest-linux-cp39-stress", "pytest-linux-cp39-unit", "pytest-windows-cp310-{hypothesis,nonreg,scripts}", "pytest-windows-cp310-compat", "pytest-windows-cp310-integration", "pytest-windows-cp310-stress", "pytest-windows-cp310-unit", "pytest-windows-cp311-{hypothesis,nonreg,scripts}", "pytest-windows-cp311-compat", "pytest-windows-cp311-integration", "pytest-windows-cp311-stress", "pytest-windows-cp311-unit", "pytest-windows-cp37-{hypothesis,nonreg,scripts}", "pytest-windows-cp37-compat", "pytest-windows-cp37-integration", "pytest-windows-cp37-stress", "pytest-windows-cp37-unit", "pytest-windows-cp38-{hypothesis,nonreg,scripts}", "pytest-windows-cp38-compat", "pytest-windows-cp38-integration", "pytest-windows-cp38-stress", "pytest-windows-cp38-unit", "pytest-windows-cp39-{hypothesis,nonreg,scripts}", "pytest-windows-cp39-compat", "pytest-windows-cp39-integration", "pytest-windows-cp39-stress", "pytest-windows-cp39-unit", "wheel-cp310-manylinux_x86_64", "wheel-cp310-win_amd64", "wheel-cp311-manylinux_x86_64", "wheel-cp311-win_amd64", "wheel-cp36-manylinux_x86_64", "wheel-cp37-manylinux_x86_64", "wheel-cp37-win_amd64", "wheel-cp38-manylinux_x86_64", "wheel-cp38-win_amd64", "wheel-cp39-manylinux_x86_64", "wheel-cp39-win_amd64". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime

Name	Size
build-metadata-build-python-wheels-linux-cp310	324 MB
build-metadata-build-python-wheels-linux-cp311	324 MB
build-metadata-build-python-wheels-linux-cp36	326 MB
build-metadata-build-python-wheels-linux-cp37	326 MB
build-metadata-build-python-wheels-linux-cp38	323 MB
build-metadata-build-python-wheels-linux-cp39	324 MB
build-metadata-build-python-wheels-windows-cp310	440 MB
build-metadata-build-python-wheels-windows-cp311	440 MB
build-metadata-build-python-wheels-windows-cp37	440 MB
build-metadata-build-python-wheels-windows-cp38	440 MB
build-metadata-build-python-wheels-windows-cp39	438 MB
build-metadata-cpp-tests-linux-default	3.16 GB
build-metadata-cpp-tests-windows-default	48.8 MB
pytest-linux-cp310-compat	18 KB
pytest-linux-cp310-integration	337 KB
pytest-linux-cp310-stress	34.8 KB
pytest-linux-cp310-unit	0 Bytes
pytest-linux-cp310-{hypothesis,nonreg,scripts}	27.2 KB
pytest-linux-cp311-compat	18 KB
pytest-linux-cp311-integration	337 KB
pytest-linux-cp311-stress	34.5 KB
pytest-linux-cp311-unit	0 Bytes
pytest-linux-cp311-{hypothesis,nonreg,scripts}	27.1 KB
pytest-linux-cp36-integration	343 KB
pytest-linux-cp36-integration-compat36	343 KB
pytest-linux-cp36-stress	35.1 KB
pytest-linux-cp36-stress-compat36	35.1 KB
pytest-linux-cp36-unit	0 Bytes
pytest-linux-cp36-unit-compat36	0 Bytes
pytest-linux-cp36-{hypothesis,nonreg,scripts}	27.5 KB
pytest-linux-cp36-{hypothesis,nonreg,scripts}-compat36	27.5 KB
pytest-linux-cp37-compat	18.1 KB
pytest-linux-cp37-integration	343 KB
pytest-linux-cp37-stress	35.1 KB
pytest-linux-cp37-unit	0 Bytes
pytest-linux-cp37-{hypothesis,nonreg,scripts}	27.4 KB
pytest-linux-cp38-compat	18 KB
pytest-linux-cp38-compat-compat38	18 KB
pytest-linux-cp38-integration	337 KB
pytest-linux-cp38-integration-compat38	337 KB
pytest-linux-cp38-stress	34.8 KB
pytest-linux-cp38-stress-compat38	34.8 KB
pytest-linux-cp38-unit	0 Bytes
pytest-linux-cp38-unit-compat38	0 Bytes
pytest-linux-cp38-{hypothesis,nonreg,scripts}	27.1 KB
pytest-linux-cp38-{hypothesis,nonreg,scripts}-compat38	27.1 KB
pytest-linux-cp39-compat	18 KB
pytest-linux-cp39-integration	337 KB
pytest-linux-cp39-stress	34.8 KB
pytest-linux-cp39-unit	0 Bytes
pytest-linux-cp39-{hypothesis,nonreg,scripts}	27.1 KB
pytest-windows-cp310-compat	19.3 KB
pytest-windows-cp310-integration	325 KB
pytest-windows-cp310-stress	36.6 KB
pytest-windows-cp310-unit	0 Bytes
pytest-windows-cp310-{hypothesis,nonreg,scripts}	20.2 KB
pytest-windows-cp311-compat	19.3 KB
pytest-windows-cp311-integration	605 KB
pytest-windows-cp311-stress	36.4 KB
pytest-windows-cp311-unit	0 Bytes
pytest-windows-cp311-{hypothesis,nonreg,scripts}	20.1 KB
pytest-windows-cp37-compat	19.3 KB
pytest-windows-cp37-integration	319 KB
pytest-windows-cp37-stress	36.6 KB
pytest-windows-cp37-unit	0 Bytes
pytest-windows-cp37-{hypothesis,nonreg,scripts}	20.2 KB
pytest-windows-cp38-compat	19.3 KB
pytest-windows-cp38-integration	605 KB
pytest-windows-cp38-stress	36.6 KB
pytest-windows-cp38-unit	0 Bytes
pytest-windows-cp38-{hypothesis,nonreg,scripts}	20.2 KB
pytest-windows-cp39-compat	19.3 KB
pytest-windows-cp39-integration	605 KB
pytest-windows-cp39-stress	36.6 KB
pytest-windows-cp39-unit	0 Bytes
pytest-windows-cp39-{hypothesis,nonreg,scripts}	20.2 KB
wheel-cp310-manylinux_x86_64	16.3 MB
wheel-cp310-win_amd64	7.19 MB
wheel-cp311-manylinux_x86_64	16.3 MB
wheel-cp311-win_amd64	7.16 MB
wheel-cp36-manylinux_x86_64	16.4 MB
wheel-cp37-manylinux_x86_64	16.4 MB
wheel-cp37-win_amd64	7.17 MB
wheel-cp38-manylinux_x86_64	16.3 MB
wheel-cp38-win_amd64	7.19 MB
wheel-cp39-manylinux_x86_64	16.3 MB
wheel-cp39-win_amd64	7.16 MB

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Building 2087/merge on pull_request by vasil-pashov #8846

Summary

Building 2087/merge on pull_request by vasil-pashov #8846

Jobs

Run details

build.yml

Annotations

Artifacts