The path to mysql.exe changed. Fortunately, chocolately puts the folder
containing the exe in the PATH environment variable, so we don't even
need to provide an absolute path.
See ef6bbaa. We previously ran into crashes that are apprently related to a
decrease in memory on never runners. The crash can be avoided by increasing the
swap file.
Closes GH-12267
Keep this up to date in all non-security-only branches, because the node.js
runtime for older versions might get deprecated in the future and fixing this
for all branches at once is easier.
This allows https://nielsdos.github.io/php-benchmark-visualisation/ to only
show commits from master (or a specific branch). Otherwise we get confusing,
undulating commits from different branches, with potentially wildly different
performance.
Closes GH-12101
We get the following errors:
profiling:./ext/pdo_oci/.libs/oci_statement.gcda:Cannot open
...
It seems these extensions were never tested for coverage. Having coverage here
would be nice, but since they are not actively worked on I don't want to
investigate the issue.
On one of the nightly CI builds last week, there were test failures in
mbstring which appear like they might be related to SIMD-accelerated
code. The function which failed testing has multiple implementations,
and the specific implementation which is used depends on the features of
the host CPU and the build configuration.
The CI build log does not offer any clues about what implementation
was actually used when the tests failed. If the same thing happens
again, it will be helpful to (at least) know what CPU features the host
CPU supports. This will also be helpful when diagnosing any other CI
build failures which relate to CPU-specific code (or those which
related to external packages such as ICU).
It would be better to print even more information about the build
configuration. It would also be better to print host CPU information
on Windows CI builds as well.
Within the entire repository these are documentation files and CI don't
need to run when they are changed.
This now includes also README.REDIST.BINS, README.md, and similar README
files within the sapi and ext directories.
README files in tests directories are also only for internals
documentations purposes.
Cirrus will no longer offer unlimited free builds starting next month. We don't
have an alternative for FreeBSD and ARM, so move what we can for now.
Closes GH-11898
It should be incredibly rare for something to fail only without opcache while
also being platform specific. We're keeping opcache-less tests for x64 Linux,
macOS and i386 will continue to be tested without opcache in nightly.
Closes GH-11867
