Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-07-07 | SL-18837: Try putting generated Python scripts in RUNNER_TEMP dir. | Nat Goodspeed | |
The claim is that the Windows Python interpreter is integrated somehow with the OS such that a command line that tries to run Python with a script that "looks suspicious" (i.e. in a system temp directory) fails with "Access denied" without even loading the interpreter. At least that theory would explain the "Access denied" errors we've been getting trying to run Python scripts generated into the system temp directory by our integration tests. Our hope is that generating such scripts into the GitHub RUNNER_TEMP directory will work better. As this test is specific to Windows, don't even bother running Mac builds. | |||
2023-07-07 | SL-18837: Use multi-line GitHub outputs to upload artifacts. | Nat Goodspeed | |
Having observed installer upload failures, I discovered the warning in actions/upload-artifact/README.md about multiple concurrent jobs trying to post the same pathname to the same artifact name. Try to disambiguate artifacts not only for different platforms, but for different jobs running on the same platform. This change also reflects my understanding that an artifact is (effectively) a distinct zip file that can contain multiple uploaded files. Because we'll want to download metadata without having to download enormous installers, create a separate metadata artifact per platform. Similarly, symbol files can get large: use a third distinct artifact for symbol files. But with those artifacts defined, leverage actions/upload-artifact's ability to upload multiple paths to the same artifact. In build.sh, define bash arrays installer, metadata, symbolfile and set up so that, on exit, each is written to a GITHUB_OUTPUT variable with the corresponding name. This involves a little magic to get macOS bash 3 to indirectly access an array. These multi-line output variables are then used to drive the upload-artifact step for each of the defined artifacts. | |||
2023-07-06 | SL-18837: Ding Dong, 32-bit is dead! | Nat Goodspeed | |
2023-07-06 | SL-18837: Add addoutput, addarrayoutput functions to build.sh | Nat Goodspeed | |
and use them instead of codeticket addoutput to pass GitHub xxx_name, xxx_path outputs to build.yaml. Add upload steps to build.yaml to try to upload build products identified in build.sh. | |||
2023-06-30 | SL-18837: Unset AUTOBUILD_CONFIGURATION. | Nat Goodspeed | |
We suspect that autobuild incorrectly prioritizes AUTOBUILD_CONFIGURATION over its command-line -c switch. The autobuild command to build the TPV package for llphysicsextensions specifies -c Tpv (the configuration in the specified config file), but with AUTOBUILD_CONFIGURATION=Release set, autobuild fails: "ERROR: no configuration for build configuration 'Release' found" | |||
2023-06-30 | SL-18837: Revert "Install autobuild from source repo, not PyPI." | Nat Goodspeed | |
That doesn't seem to be the distinction between TC builds and GH builds. Instead, we'll try unsetting AUTOBUILD_CONFIGURATION. This reverts commit d62e7039dafe4a49d548225203785eeda0eeb44a. | |||
2023-06-29 | SL-18837: Install autobuild from source repo, not PyPI. | Nat Goodspeed | |
Bug in autobuild 3.9.2? The TC viewer build can successfully build llphysicsextensions/autobuild-tpv.xml, but the previous GH actions build failed: "no configuration for Release found" despite -c Tpv. The difference seems to be that we used 'pip3 install autobuild' from PyPI, whereas the TC buildscripts setup clones secondlife/autobuild branch v3 and installs from that repo. | |||
2023-06-29 | SL-18837: Temporarily suppress Windows builds; add finalize function | Nat Goodspeed | |
Also pretend novel arch value MINGW6 is really CYGWIN so we'll recognize it. | |||
2023-06-28 | SL-18837: Don't try to engage git-hooks explicitly at all. | Nat Goodspeed | |
2023-06-28 | SL-18837: Get buildscripts_support_functions from sling-buildscripts | Nat Goodspeed | |
and use these variants for GitHub builds. | |||
2023-06-28 | SL-18837: Don't fetch (unmigrated) build-secrets, use GH secrets. | Nat Goodspeed | |
2023-06-28 | SL-18837: Include actions-build-sh branch in build trigger pushes. | Nat Goodspeed | |
2023-06-27 | SL-18837: Try doing necessary setup to run viewer's own build.sh. | Nat Goodspeed | |
2023-06-07 | SL-18837 fix win32 build warning about missing python-version setting | Brad Linden | |
2023-06-07 | Attempt to port some build.yaml improvements from DRTVWR-559 over to actions ↵ | Brad Linden | |
branch | |||
2023-06-07 | SL-18837: Try to install llsd in the Python used by py.exe | Nat Goodspeed | |
2023-06-07 | SL-18837: Tell py.exe to use Python 3.9 instead of 3.11 | Nat Goodspeed | |
2023-06-07 | SL-18837: Quote integers used for environment variables | Nat Goodspeed | |
2023-06-07 | SL-18837: Try setting PY_PYTHON and PYLAUNCHER_DEBUG | Nat Goodspeed | |
which should only affect Windows unit tests, but should hopefully improve our chances that Windows unit tests will succeed. | |||
2023-06-05 | SL-18837: pip install llsd as well as autobuild. | Nat Goodspeed | |
The Python child processes used by llprocess_test.cpp and llleap_test.cpp need the Python llsd module to communicate with the C++ parent process. Also set LOGFAIL and BUGSPLAT_DB environment variables. | |||
2023-05-19 | DRTVWR-558: Merge branch 'main' of secondlife/viewer into actions | Nat Goodspeed | |
2023-05-15 | SL-18837: AUTOBUILD_GITHUB_TOKEN to authenticate private packages. | Nat Goodspeed | |
2023-03-24 | SL-18837: Try building Release viewer config on GH. | Nat Goodspeed | |
2022-11-21 | Merge pull request #4 from secondlife/signal/stale | Signal Linden | |
Close stale PRs | |||
2022-11-18 | Merge pull request #3 from secondlife/signal/label | Signal Linden | |
Add automatic PR labels | |||
2022-11-18 | Mark PRs as stale after 60 days, close them automatically if no response | Bennett Goble | |
after 7 days. | |||
2022-11-18 | Add automatic PR labels | Bennett Goble | |
2022-11-18 | Add CLA bot | Bennett Goble | |
2022-10-12 | Upload macos installer | Signal Linden | |
2022-10-12 | Build on 64-core machine | Signal Linden | |
2022-10-12 | Add macOS build back | Signal Linden | |
2022-10-12 | Build on 8-core machine | Signal Linden | |
2022-10-12 | Build on 16-core machine | Signal Linden | |
2022-10-12 | Run build with default runner | Signal Linden | |
2022-10-12 | Fix YAML syntax | Signal Linden | |
2022-10-12 | Run on windows-2022-large | Signal Linden | |
2022-10-12 | Upload installer, build Release, use large runner | Signal Linden | |
2022-10-11 | Replace llbase with llsd module | Signal Linden | |
2022-10-11 | Omit macOS until I have a mac laptop | Signal Linden | |
2022-10-10 | Remove cygwin artifacts | Signal Linden | |
2022-10-10 | Call load_vsvars | Signal Linden | |
2022-10-10 | Use cygwin | Signal Linden | |
2022-10-10 | Explicitly set AUTOBUILD_VSVER | Signal Linden | |
2022-10-10 | Perform source_environment | Signal Linden | |
2022-10-10 | Also build win32 with VS2k22 | Signal Linden | |
2022-10-10 | Build with VS2k22 | Signal Linden | |
2022-10-10 | Use pre-installed python | Signal Linden | |
2022-10-10 | Allow CMAKE to run autobuild install | Signal Linden | |
2022-10-10 | Force RelWithDebInfoOS configuration | Signal Linden | |
2022-10-10 | Separate autobuild install from build | Signal Linden | |