Skip to content
Coordinator DB
View as Markdown
View as Markdown

Validate a LoongArch distribution ​

For a LoongArch-targeted executable, record both where it was produced and where it was executed. Include the target operating system and machine details. Cross-build completion and target-side behavior are distinct results; neither should be inferred from the other.

Use installation as the current installation reference. Keep the executable and supplied configuration in a test directory with a disposable database.

Verify configuration and SQL ​

sh
./coordinator serve --config-file config.xml --db loongarch-check.db

In another terminal, run:

sh
./coordinator client --database data --query "SELECT 'configuration loaded' AS result FORMAT csv"

Expect "configuration loaded". A successful request establishes that startup, authentication and a simple result worked in that environment.

Expand to the application's use case ​

Check writes, a reconnect and the input/output formats your application depends on. If the executable cannot launch, preserve that error separately from any SQL test results. When moving files between machines, verify configuration and database paths explicitly; see configuration files. Submit the exact failing case with its environment rather than presenting an untested target as supported.