Age | Commit message (Collapse) | Author |
|
actions/cache@v3
actions/checkout@v3
actions/upload-artifact@v3
actions/setup-dotnet@v2
actions/setup-java@v3
actions/setup-python@v4
mymindstorm/setup-emsdk@v11
Also reset cache keys as we're going to cleanup all caches.
|
|
Fully removes the `bits` option and adapts the code that relied on it.
Co-authored-by: Rémi Verschelde <rverschelde@gmail.com>
|
|
Corrects prior regression which caused ERROR output and exit code of 1.
|
|
GitHub Actions runners only have 14 GiB available, so we need
to keep the cache constrained.
|
|
And force a full rebuild as the cache is now broken.
|
|
And force rebuild of Linux cache which got corrupted...
|
|
This allows having good stacktraces when the tests crash.
|
|
|
|
|
|
|
|
|
|
https://github.com/SCons/scons/releases/tag/4.1.0
|
|
We often hit "Too Many Requests" errors when uploading the cache with
`actions/cache` because there's a limit of 10 GB every 5 minutes, and we can
easily go over it when we amend or merge several PRs in a short timespan.
This will make the CI artifacts less useful for debugging crashes but there's
no real way around this.
|
|
|
|
It's normally opt-in as the advanced one (CTL support) is the default,
but we need to build it to catch potential build issues.
|
|
|
|
This keeps their size small and allows to compare size changes on templates
in PRs, as the template size is what is most relevant to users.
For editor builds we keep debug symbols so they can be used to debug crashes.
|
|
|
|
Set retention-days of all artifacts to 14.
|
|
This can be used to compare impacts on the generated files
and especially their size in PRs.
|
|
|
|
|
|
|
|
Implements exit codes into the engine so tests can return their statuses.
Ideally we don't do this, and we use FIXUP logic to 'begin' and 'end' the engine execution for tests specifically.
Since realistically we're initialising the engine here we don't want to do that, since String should not require an engine startup to test a single header.
This lowers the complexity of running the unit tests and even for
physics should be possible to implement such a fix.
|
|
The base branch is hardcoded as an env variable as I couldn't find a simple
way to just get either `3.2` or `master`. But it's easy to change when we
branch off from `master` to a new stable branch, which doesn't happen often.
(There's `{{github.base_ref}}` but it's probably more verbose like
`ref/heads/master`, and only valid for PRs.)
|
|
|
|
|
|
|