| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* anders/diameter/test/OTP-16752:
Rework remaining diameter testsuites
Rework diameter_{dist,distribution,examples}_SUITE
Rework diameter_{traffic,tls,transport}_SUITE
Simplify diameter_util
Run fewer testcases in diameter_traffic_SUITE
Remove is_port guard
Skip diameter_gen_sctp_SUITE
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As in the previous two commit: remove common_test as a requirement and
make all testcases independent. Add a make target for running any suite
without common test; for example, to run all testcases in
diameter_dpr_SUITE:
make _dpr
Similar to the target that runs suites with common_test, just add an
underscore prefix.
|
| |/ |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In particular, that the association id received in messages on a
one-to-one socket after peeloff may be different from the id received on
the listen socket at comm_up.
This seems odd, since it's then not possible to send until the id is
discovered by reception of an SCTP message containing it, but it's
unclear if this is a bug or a feature, or if it's specific to certain
platforms. Treat it as a feature in this commit, and get the association
id as mentioned, an incoming CER being expected before anything is sent.
Commit da3e5d67 has more history.
|
| |
|
|
|
|
|
|
|
|
| |
In particular, that transmission can be very slow. The problem appears
to be linked to sndbuf/recbuf, but even with buffers that are large
enough to hold all messages being sent, turnaround times can still vary
by hundreds of milliseconds in a reasonable test environment.
Use multiple streams and a sender process to more closely mirror the
usage in diameter_sctp, but neither is the source of the problems.
|
| |
|
|
|
|
|
|
|
|
|
| |
That missed comm_up when something like the following was received on
FreeBSD (for one):
{sctp,#Port<0.599>,
{127,0,0,1},
45455,
{[{sctp_sndrcvinfo,0,0,[],0,0,0,0,145060462,3}],
{sctp_assoc_change,comm_up,0,10,10,3}}}
|
| |\
| |
| |
| |
| |
| |
| | |
The diffs are all about adapting to the OTP 18 time interface. The code
was previously backwards compatible, falling back on the erlang:now/0 if
erlang:monotonic_time/0 is unavailable, but this was seen to be a bad
thing in commit 9c0f2f2c. Use of erlang:now/0 is now removed.
|
| | |
| |
| |
| |
| | |
By doing away with more wrapping that the parent commit started to
remove.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
OTP-12845
* bruce/change-license:
fix errors caused by changed line numbers
Change license text to APLv2
|
| | |/ |
|
| |/ |
|
| |\
| |
| |
| |
| |
| | |
* anders/diameter/time/OTP-12439:
Use new time api in test suites
Use new time api in implementation
|
| | |
| |
| |
| |
| |
| | |
Where it's less important to do so, but it has to be done at some point
since erlang:now/0 is deprecated. As in the parent commit, continue to
use the old api if the new one is unavailable.
|
| |/
|
|
|
|
| |
More than an incoming message can contain ancillary data, which the
gen_sctp and transport suites did not expect. On FreeBSD 10, an
sctp_assoc_change event appears always to contain ancillary data.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
* anders/diameter/R15B02_release:
Dialyzer spec fix
Learn to keep time in diameter_gen_sctp_SUITE
Update command line test for changed ct:run_test/1 return value
OTP-10243
|
| | |
| |
| |
| | |
Microseconds /= milliseconds.
|
| |/
|
|
|
| |
This improves the situation with long turnaround times but doesn't
completely solve the problem.
|
| |
|
|
| |
To the R15 behaviour, with a return value instead of badarg.
|
|
|
Commit e05868f49b442c10cedbded390c110473cda6f00 was the original,
this commit is the result of splitting that one in two.
Resurrect this suite to make SCTP faults more visible: the transport
suite has sporadic failures because of them, despite having jacked
up timeouts to unreasonable values.
|
