| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Install binary build from upstream.
|
|
|
|
|
|
|
|
|
| |
Github has now dropped support for running jobs on Ubuntu 18.04 and
these jobs now sit un-run for a day and then fail.
Hopefully many of these jobs can be resurrected on a newer Ubuntu
version, but as a first step let's get git master back to a state where
all the enabled jobs can be expected to pass.
|
|
|
|
| |
Should fix slew of warnings that "Node.js 12 actions are deprecated"
|
|
|
|
|
| |
PHP7 security support ended 2022-11-28 so it doesn't make sense to
include support for it in the SWIG 4.2.x release series.
|
|
|
|
| |
This reverts commit ef4c61c23cb2b3e8fe4238a21f275081ae0cfd3b.
|
|
|
|
| |
Waiting for URL redirects to be put in place.
|
|
|
| |
Signed-off-by: Alex <aleksandrosansan@gmail.com>
|
|\
| |
| | |
Update Windows CMake builds to use NuGet package for PCRE2
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Tests are now passing there.
|
| |
| |
| |
| | |
Tests are now passing there.
|
| |
| |
| |
| |
| | |
I'm actively working on fixing them, but meanwhile we don't want PR
jobs failing on these.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The CI job for PHP 8.0 was relying on not specifying a version
giving us PHP 8.0, but actually it gives us 8.1 currently.
This seems too brittle, so always specify the version explicitly as
at worst it means uninstalling and reinstalling PHP packages in a
case we could avoid.
Also add PHP 8.2 testing.
See #2383
|
| |
| |
| | |
Signed-off-by: sashashura <93376818+sashashura@users.noreply.github.com>
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Add testing for javascriptcoregtk-4.1.
Simplify configure detection of JSC, relying only only pkg-config.
Add javascriptcoregtk-4.1 tests to GHA.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Closes #2314
|
| |
| |
| |
| |
| |
| | |
This was created by fc6269a3cad26acbb62f7eff8b3a218433fc5554 which
converted the non-functioning Octave 6.4 into a duplicate of the
other Octave build instead of dropping it completely.
|
| |
| |
| |
| |
| |
| |
| | |
Prevent GC from collecting "hello" string in testcase
as workaround to prevent GC occasionally causing segfault.
Issue #2115
|
| | |
|
| |
| |
| |
| | |
Seems broken atm
|
| |
| |
| |
| |
| | |
octave-6.4 has disappeared - stop testing it.
ruby-2.6 allow to fail (for li_std_set), see issue #2115.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
./configure now enables C++11 and later C++ standards testing by default (when
running: 'make check').
The options to control this testing are the same:
./configure --enable-cpp11-testing
./configure --disable-cpp11-testing
But the former is now the default and the latter can be used to turn off C++11 and
later C++ standards testing.
Reduce the number of tests on Appveyor by only running 32-bit (x86) using
latest Visual Studio (2022). Drop 32-bit Cygwin and MinGW testing.
Add C# and Java testing on VS2022 and drop Java testing on older Visual Studio.
This reduces the really long run times on Appveyor, however, VS2022 is
somewhat slower than older compilers.
|
|
|
|
|
|
|
| |
MzScheme headers have a problem when using -Werror that the test-suite uses:
/usr/include/racket/sconfig.h:126:43: error: invalid suffix on literal; C++11 requires a space between literal and string macro [-Werror=literal-suffix]
126 | # define SCHEME_PLATFORM_LIBRARY_SUBPATH "x86_64-"SPLS_LINUX
|
| |
|
|
|
|
|
| |
Test c++17 on Github Actions to try keep it passing when
configure detects g++ can test c++17.
|
|
|
|
|
| |
Test c++17 on Github Actions to try keep it passing when
configure detects g++ can test c++17.
|
|
|
|
|
|
|
| |
Specify PY2=1 to use Python 2.
See #1779
Closes #2235
|
|
|
|
|
|
| |
Set it so it should be visible where the CI log shows the environment,
as `make` is run with `-s` so the compile command lines are unhelpfully
not shown.
|
|
|
|
|
|
|
|
|
| |
It seems too brittle to enable by default as we'd have to avoid
including any system headers after doh.h, which is hard to enforce,
but just having it enabled for one CI job should avoid uses of the
poisoned symbols from being accidentally introduced.
See #2223
|
|
|
|
| |
We limit target language to one version for c++11 and c++14 testing
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit log Scilab version at ./configure to ease maintenance. It
uses Scilab include next to the bin directory which will work for both
system-wide install and binaries from scilab.org.
SCILAB_VERSION is define as an automake variable for easier
failure investigation.
Note: the Ubuntu Scilab version is used when available, in the current
CI config there is:
* Scilab 5.5 from scilab.org
* Scilab 6.0 from Ubuntu 18.04
* Scilab 6.1 from Ubuntu 20.04
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
We only support v8 5.0 and later now.
libv8-dev is no longer packaged in newer Ubuntu releases, so it
seems there isn't an easy way to update this to test a supported
v8 version, but really v8 via node is the configuration people will
actually use anyway.
|