| Age | Commit message (Collapse) | Author |
|---|
|
By examining which modules *use* runtime and compiler modules instead of
which modules compiler modules call. Note that the semantics are changed
somewhat: we will now fail if diameter modules are called from an
application which diameter.app lists as a start dependency, which wasn't
the case previously.
|
|
In particular, that modules listed in the 'modules' tuple only call
modules in other applications listed in the 'runtime_dependencies'
tuple.
|
|
Due to sporadic timeouts one some (slow) hosts.
|
|
The workaround (commit 57d5564f) was to dialyzer only understanding
nowarn_unused_function on individual functions. This is no longer the
case as of R15B01 (commit 477fd95a).
|
|
Depending on the dictionary, generated dictionary modules may contain
unused functions included from diameter_gen.hrl. There may still be
warnings however since even used functions can contain code that
isn't reached for a given dictionary.
It would be useful for diameter to generate spec attributes for
a dictionary's generated records but the format of these is currently
undocumented.
|
|
|
|
After having added a less than stellar dependency that broke the
build. Parallel make could succeed by chance but not sequential.
This ensures the error doesn't get past test.
|
|
|
|
* anders/diameter/release_R15A:
Version -> 0.11, update appup, minor app suite fix
|
|
|
|
A recent sasl change results in a missing_sasl warning/error that
causes the release and relup testcases to fail.
|
|
As a module-based alternative to the escript diameterc.
|
|
Also update app testsuite to allow for "undefined" calls
from diameter_tcp to ssl.
|
|
|
|
|
|
|
|
|
|
|
