[ci] upgrading to pv6 #1525
Annotations
29 errors and 4 warnings
|
test-build-windows
The operation was canceled.
|
|
test-build-windows
Canceling since a higher priority waiting request for test_build-refs/pull/1118/merge exists
|
|
test-build-ubuntu (ubuntu-22.04)
The operation was canceled.
|
|
test-build-ubuntu (ubuntu-22.04)
Canceling since a higher priority waiting request for test_build-refs/pull/1118/merge exists
|
|
test-build-ubuntu (ubuntu-24.04)
The operation was canceled.
|
|
test-build-ubuntu (ubuntu-24.04)
Canceling since a higher priority waiting request for test_build-refs/pull/1118/merge exists
|
|
test-build-macos (macos-14)
<cfloat> tried including <float.h> but didn't find libc++'s <float.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
<cerrno> tried including <errno.h> but didn't find libc++'s <errno.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
<cstdio> tried including <stdio.h> but didn't find libc++'s <stdio.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
<cwchar> tried including <wchar.h> but didn't find libc++'s <wchar.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
<cwctype> tried including <wctype.h> but didn't find libc++'s <wctype.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
<cctype> tried including <ctype.h> but didn't find libc++'s <ctype.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library.
|
|
test-build-macos (macos-14)
<cstring> tried including <string.h> but didn't find libc++'s <string.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
<cstdlib> tried including <stdlib.h> but didn't find libc++'s <stdlib.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
<cstddef> tried including <stddef.h> but didn't find libc++'s <stddef.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
<cmath> tried including <math.h> but didn't find libc++'s <math.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-14)
Canceling since a higher priority waiting request for test_build-refs/pull/1118/merge exists
|
|
test-build-macos (macos-15)
<cfloat> tried including <float.h> but didn't find libc++'s <float.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
<cerrno> tried including <errno.h> but didn't find libc++'s <errno.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
<cstdio> tried including <stdio.h> but didn't find libc++'s <stdio.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
<cwchar> tried including <wchar.h> but didn't find libc++'s <wchar.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
<cwctype> tried including <wctype.h> but didn't find libc++'s <wctype.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
<cctype> tried including <ctype.h> but didn't find libc++'s <ctype.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library.
|
|
test-build-macos (macos-15)
<cstring> tried including <string.h> but didn't find libc++'s <string.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
<cstdlib> tried including <stdlib.h> but didn't find libc++'s <stdlib.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
<cstddef> tried including <stddef.h> but didn't find libc++'s <stddef.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
<cmath> tried including <math.h> but didn't find libc++'s <math.h> header. This usually means that your header search paths are not configured properly. The header search paths should contain the C++ Standard Library headers before any C Standard Library, and you are probably using compiler flags that make that not be the case.
|
|
test-build-macos (macos-15)
Canceling since a higher priority waiting request for test_build-refs/pull/1118/merge exists
|
|
test_build
Canceling since a higher priority waiting request for test_build-refs/pull/1118/merge exists
|
|
test-build-macos (macos-14)
sqlite 3.50.4 is already installed and up-to-date.
To reinstall 3.50.4, run:
brew reinstall sqlite
|
|
test-build-macos (macos-14)
ninja 1.13.1 is already installed and up-to-date.
To reinstall 1.13.1, run:
brew reinstall ninja
|
|
test-build-macos (macos-15)
sqlite 3.50.4 is already installed and up-to-date.
To reinstall 3.50.4, run:
brew reinstall sqlite
|
|
test-build-macos (macos-15)
ninja 1.13.1 is already installed and up-to-date.
To reinstall 1.13.1, run:
brew reinstall ninja
|