| Age | Commit message (Collapse) | Author |
|---|
|
|
|
We already have one on Cirrus, and it works fine.
|
|
|
|
Using ~0 involves a bitwise operation on int, so depends on
the internal representation of signed integers.
|
|
|
|
- Bump FreeBSD to 12.1.
- Simplify stage1 logic.
- Re-try downloading the image from a different mirror if one fails.
- Use the `expect` utility instead of dealing with screen's log file.
- Re-run failed toxcore test one more time and in sequence.
|
|
|
|
|
|
Removed av_test, because it depends on an ancient opencv that starts to
really not exist on modern systems anymore.
|
|
|
|
We can't see the failure messages now, so something like "aborted", which
probably means assertion failure, is not very useful right now.
E.g. https://travis-ci.org/TokTok/c-toxcore/jobs/476028600#L1220
|
|
|
|
|
|
tox-bootstrapd can use around 600 TCP sockets during TCP server's normal
functioning. Many systems default to having a soft limit of 1024 open file
descriptors, which we are close to reaching, so it was suggested we bump that
limit to a higher number. iphy suggested increasing it to 32768.
|
|
|
|
|
|
|
|
That way CMake's behavior matches what autotools does -- letting
toxcore/logger.h handle the default case.
|
|
|
|
|
|
We should avoid recursion, as it makes reasoning about stack growth
harder. This tool shows (currently) 4 (non-tail) recursive functions, at
least 2 of which are easy to fix.
|
|
|
|
|
|
With distcheck, it's all or nothing, so we build with -j50 and run tests
with -j50.
|
|
Not only the second time it fails.
|
|
We check that:
* The license is GPLv3.
* .travis.yml conforms with the toktok style specification.
* There exists a README.md file.
|
|
|
|
Instead of importing a well-known file. This gives toktok-stack more
freedom in where and how it wants to define its interface, as long as it
provides the configurations requested ("linux" and "clang").
|
|
This checks that (some of) the code follows some simplicity and naming
guidelines set by the tool.
|
|
These always fail at present. We'll need to look into making them not
always fail so we can enable them and get some useful signal from them.
|
|
This uses a single .cc file containing almost all the code in the
repository to perform whole program analysis.
|
|
These flags are needed so the code actually compiles, so can't only be
set on Travis.
|
|
|
|
Also some other cleanups. This PR means that future PRs, i.e. the PGC PR,
must not break the rules established here.
|
|
|
|
Most of the auto-tests should use this fixture, but I've only done a few
to set an example.
|
|
Have one script per build. This means more duplication between the
scripts, but it's much easier to understand and to run locally.
|
