The latter are deprecated and shouldn't be used any longer.
No real changes.
See #23537.
(cherry picked from commit a0e3f1e1aba5fd7858936773f09d96ae63041381)
10.15 is being phased out by GitHub, so switch to the still supported
runner platform version.
Closes#22698.
(cherry picked from commit 4e26568f9727936d3c84b1f3689086f07ff71878)
Switch to a local fork of the action using node 16 and latest
actions/core package as both are necessary to avoid getting deprecation
warnings.
(cherry picked from commit f044e5cab348d687c81d905949b9c6c9f2ce9422)
This build is the one which risks getting broken the most as it's so
little used, so we must have a test for it in the CI.
Also enable 2.8 compatibility for it under assumption that people
disabling Unicode support must be working with legacy code bases.
The first unit test using wxWebView sometimes fails in other builds too,
so try using the same hack as was previously used for the clang build
for them as well.
(cherry picked from commit 3ac39970b1e9c30c5d339d8a03d19d1d4fba504d)
Since 8.0~repack-3 version of the Debian Wine package, installing wine64
doesn't create wine64 symlink any more and wine package needs to be
installed to do it, apparently due to the changes done to fix
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029536
This resulted in the tests not running any more because we used wine64
for running them. Just use "wine" now and install wine package, as it
should still run 64-bit binaries just fine.
(cherry picked from commit 28e0a7e01debf01e8f42524b6071714b7778c6c6)
Work around the problem which was previously hidden by 07dfc18cc0
(Disable wxWebView in ASAN CI build, 2021-01-31) by building the webkit
extension shared library without ASAN.
This should ideally be handled at the build system level, but this seems
difficult to do, so use this hack for now -- it at least ensures that
wxWebView unit tests are tested with ASAN too.
(cherry picked from commit 8ee559430b11008ec3825d8470aa281808091b37)
Ubuntu 18.04 runner environment is being deprecated, so use a container
running inside the latest Ubuntu runner environment instead.
This is a combined cherry-pick of several commits merged into master as
part of e6dfd9748f (Merge branch 'ci-use-containers', 2022-10-10)
excluding those removing pre-C++11 support, which is still needed in
this branch.
Avoid flagging the use of "override" in a comment as a C++11 keyword by
stripping the comments before checking for the keywords forbidden in
this branch.
This is not 100% correct and doesn't deal with multiline comments at
all, but we use the latter ones rarely and it's not worth the effort to
add support for them here.
This backports changes already done in master and upgrades to the
currently supported versions of the different actions, most importantly
actions/checkout one.
The previous bug fix fixes updating an existing release, but broke
creating the new ones, which wasn't ideal.
(cherry picked from commit 31720e1ee102b195265203f9e9886929bff0528d)
Now that we don't use Travis CI any longer (and don't use httpbin on the
other CI providers yet), we can make our life much simpler by just using
Python 3.10 on all platforms instead of trying to find version-specific
workarounds for various python/pip/httpbin incompatibilities.
Closes#22726.
(cherry picked from commit 458dc814c241066323858182e55d2186d396c09d)
Add the ABI files generated by libabigail abidw tool (note that
--no-corpus-path --no-comp-dir-path options were used to avoid having
system-specific object file paths in these files and the source file
paths were edited to remove the system-specific prefix from them too)
and a script comparing the current ABI with these files.
Also update the documentation to describe using libabigail tools as
abi-compliance-checker doesn't seem to work under the recent systems any
longer: it gives some warnings and doesn't detect ABI-incompatible
changes.
Closes#22634.
Wine 7.0 and later doesn't find the command if the extension is omitted
any longer, unlike the previous versions.
(cherry picked from commit 623a68c8fa869205ba469111e2f5182cb4705f73)
Import the theme files into a subdirectory without any changes, even not
removing the trailing whitespace, to facilitate updating them in the
future. Do not add the theme as a submodule as it's surprisingly big
(~12MB) and we don't want to spend extra time on cloning it in each of
our CI builds.
Using this theme gives a nicer appearance and supports the often
requested dark mode.
Remove all colour-related options from the existing custom CSS file as
they don't work well in dark mode.
Also switch to using SVGs with transparent background, rather than PNGs,
for the class diagrams, to avoid background colour mismatch in dark
mode.
This fixes the problem with empty descriptions in the annotated class
list and is a prerequisite for using custom CSS theme in the upcoming
commits.
Closes#22288.
Restrict the GitHub token permissions only to the required ones, i.e.
just read-only access to the code.
This is done in order to reduce the potential harm in case of a
malicious pull request, see GitHub blog post at
https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
Signed-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com>
Closes#22574.
Some things that seem too obvious to say apparently are not, so do say
them explicitly, as having the leftover from the template in the bug
reports is really confusing.
This seems to have been accidentally added in 6afd2e8f87 (Revert "making
sure CI builds don’t contaminated checked out directory on self-hosted
runner", 2022-04-17).
Update ccache-action to a not yet released version including the fix for
failing the entire CI job if saving the cache failed -- this shouldn't
happen at all, but in practice it does happen from time to time, and
it's better to succeed, rather than fail in this case.
The apparently innocuous a0d1379a57 (Split wxDC::GetTextExtent() test
case in 3 pieces, 2022-03-29) has broken the CI builds because it moved
the code failing under Wine (apparently due to problems in metafile
support implementation) into a differently named test.
Fix this now by excluding the right test.
This should hopefully help to speed up this build as well.
Unfortunately we can't easily use ccache for the Mac builds because this
requires having brew installed and we don't have it currently.
We probably can use it for CMake workflow but this probably requires
some arcane way of configuring CMake to use ccache that I'm not aware
about and would need to be done by someone else.
