Mike Gerwitz
fb5947d59e
It's a tad embarrassing that this has been eluding me for quite some time. I happened to run into it while testing the previous commit, which in turn only existed because I was trying to optimize runner performance. We'd have situations where, following a runner reload (exit code 129 = SIGHUP), the build would simply hang indefinitely. Apparently, `tame`, in `command-runner`, blocks on a `read` without a timeout, expecting that the FIFO attached to stdin will close if the runner crashes. Maybe that used to be the case, but that is no longer true today. Because of that, the FIFO stays open, and read continues to block, waiting for `DONE`. Now, `tamed`, when seeing that a runner has crashed (which could have been due to a reload), will check to see if that runner is marked busy. If so, that means that the client `tame` did not see `DONE`, because it did not clear the flag via `command-runner`'s `mark-available.` To notify the client that someone went wrong, `tamed` will inject a `DONE` into the output FIFO, which will allow the client to fail properly. `dslc` catches exceptions and should output `DONE` under normal operating conditions. However, since some of our systems require so much memory to build, we may encounter the OOM killer. In that case, the process has no time to recover (it is killed with SIGKILL), and therefore cannot output `DONE`. I suspect this is what has been happening to cause occasional build hangs. One final thing to clean this up: since we're properly handling reloads now, based on this commit and the immediately preceding one, we can suppress the warning when the code is 129 (see comments). DEV-10806 |
||
|---|---|---|
| bin | ||
| build-aux | ||
| core | ||
| design/tpl | ||
| doc | ||
| progtest | ||
| rater | ||
| src | ||
| tamer | ||
| test | ||
| tools | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .rev-xmle | ||
| .rev-xmlo | ||
| COPYING | ||
| COPYING.FDL | ||
| HACKING | ||
| Makefile.am | ||
| README.md | ||
| RELEASES.md | ||
| VERSION.in | ||
| bootstrap | ||
| c1map.xsd | ||
| configure.ac | ||
| package-lock.json | ||
README.md
TAME
TAME is The Algebraic Metalanguage, a programming language and system of tools designed to aid in the development, understanding, and maintenance of systems performing numerous calculations on a complex graph of dependencies, conditions, and a large number of inputs.
This system was developed at Ryan Specialty Group (formerly LoVullo Associates) to handle the complexity of comparative insurance rating systems. It is a domain-specific language (DSL) that itself encourages, through the use of templates, the creation of sub-DSLs. TAME itself is at heart a calculator—processing only numerical input and output—driven by quantifiers as predicates. Calculations and quantifiers are written declaratively without concern for order of execution.
The system has powerful dependency resolution and data flow capabilities.
TAME consists of a macro processor (implementing a metalanguage), numerous compilers for various targets (JavaScript, HTML documentation and debugging environment, LaTeX, and others), linkers, and supporting tools. The input grammar is XML, and the majority of the project (including the macro processor, compilers, and linkers) is written in a combination of XSLT and Rust.
TAMER
Due to performance requirements, this project is currently being reimplemented in Rust. That project can be found in the tamer/ directory.
Documentation
Compiled documentation for the latest release is available via our GitLab mirror, which uses the same build pipeline as we do on our internal GitLab instance. Available formats are:
Getting Started
To get started, make sure Saxon version 9 or later is available and its path
set as SAXON_CP; that the path to hoxsl is set via HOXSL; and then run
the bootstrap script:
$ export SAXON_CP=/path/to/saxon9he.jar
$ export HOXSL=/path/to/hoxsl/root
$ ./boostrap
Running Test Cases
To run the test cases, invoke make check (or its alias, make test).
Testing Core Features
In order to run tests located at core/test/core/**, a supporting environment
is required. (e.g. mega rater). Inside a supporting rater, either check out a
submodule containing the core tests, or temporarily add them into the
submodule.
Build the core test suite summary page using:
$ make rater/core/test/core/suite.html
Visit the summary page in a web browser and click the Calculate Premium button. If all test cases pass, it will yield a value of $1.
Hacking
Information for TAME developers can be found in the file HACKING.
License
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.