ci: verify Tessera remotely against the separated Aster engine
Verify Tessera GUI / verify (push) Failing after 0s
Verify Tessera GUI / verify (push) Failing after 0s
This commit is contained in:
@@ -32,7 +32,7 @@ Initialize the Aster submodule first, following the SSH identity instructions in
|
||||
git submodule update --init --recursive
|
||||
```
|
||||
|
||||
In the designated build or validation environment:
|
||||
For local native builds and window runs (automated tests run only in CI):
|
||||
|
||||
```bash
|
||||
cargo run --release
|
||||
@@ -102,3 +102,7 @@ The first parser intentionally supports only enough syntax to test the architect
|
||||
- `gap`, `padding`, and `.title`
|
||||
|
||||
There are no files, HTML, CSS, JavaScript, DOM, or resource-network concepts in the runtime.
|
||||
|
||||
## Validation
|
||||
|
||||
Local Cargo builds and native window runs are allowed; do not run local tests or Docker. Automated tests and Clippy run in [.gitea](.gitea/README.md) on ces-control using Dockerfile.ci. The Linux CI checks portable code and software-renderer tests, not macOS window presentation. Aster dependency unit tests remain in Aster CI. CI bot SSH secrets are documented in .gitea/README.md.
|
||||
|
||||
Reference in New Issue
Block a user