| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The test_fuzzers.py script is very slow especially on CI. Add a mode
to the test fuzzers where it will accept many files on the command
line and test each of them in turn. This is 100s of times faster,
as it avoids all overhead from fork/exec.
It has the downside that you can't tell which input caused a crash, so
retain the old mode with --one-at-a-time option for debugging work.
|
|
|
|
|
| |
Coverage is the slowest build, moving it up puts it into the initial
tranche of builds so it finishes before the end of the build.
|
|
|
|
|
|
| |
It is slower to startup and the overall build ends up waiting for these
last 2 builds. By running them in the front of the line they can overlap
with other builds.
|
|
|
|
|
| |
Running them all takes a long time, especially in CI, and doesn't
really add much.
|
|
|
|
| |
The cache size increases will continue until hit rate improves.
|
|
|
|
|
|
|
| |
Undocumented? side effect of a small git pull depth - if more than N
new commits are pushed to master while an earlier build is running,
the old build starts failing, as when CI does the pull it does not
find the commit it is building within the checked out tree.
|
|
|
|
|
|
|
| |
This skips putting the git revision in the build.h header. This value
changing every time means we effectively disable ccache's direct mode
(which is faster than preprocessor mode) and also prevent any caching
of the amalgamation file (since version.cpp expands the macro).
|
|
|
|
| |
Even 600M is not sufficient for the coverage build
|
|
|
|
| |
Still insufficient for debug builds
|
|
|
|
|
| |
With compression disabled, the cache is too small for builds that
use debug info, and causes 100% miss rate.
|
|
|
|
| |
Since CPU is main bottleneck to the build, this is likely not helping.
|
| |
|
|
|
|
|
|
|
| |
It appears OpenSSL has a different interpretation from us of how the
message representative is formed for P-521 when given a hash to sign
that is larger than the group order; signatures generated by us do
not verify with OpenSSL and vice versa.
|
|
|
|
|
|
| |
See http://www.secg.org/sec1-v2.pdf section 4.1.6
Closes #664
|
| |
|
| |
|
|
|
|
| |
Guess we need that update or some packages just aren't found.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
Takes longer than the cross builds so usually ends up being the last
build running.
|
|/
|
|
| |
Also use 2x core count as this spends a lot of time on IO
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Drops Mingw i686 build as it runs into a problem I could not debug,
when unit_tls.cpp is compiled with -O2 it crashes with a useless
backtrace. If compiled with -g or with lower optimizations it is ok.
Replaced with Mingw x86-64.
Add mips64 build.
|
|
|
|
| |
As Ubuntu 16.04 has v1.3 and it crashes when you use -j
|
|
|
|
|
|
|
|
| |
It is stupid and slow (~50-100x slower than variable time version) but
still useful for protecting critical algorithms.
Not currently used, waiting for OSS-Fuzz to test it for a while before
we commit to it.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is suddenly 5x slower for an unknown reason
https://community.sonarsource.com/t/sonar-analysis-step-suddenly-much-5x-slower-on-travis-ci/4364
Now it either times out or else completely dominates the runtime for Travis,
either is not acceptable.
Leave the framework for using Sonar in CI for now so it is easy to test
if things have improved later. If things are still broken in a month or
two I'll probably just drop support for Sonar.
|
|
|
|
|
|
| |
The build is timing out. Use -Os instead of -O3 in an attempt to
speed up the build step, and enable multithreaded analysis as
that step is also quite slow.
|
| |
|
| |
|
|
|
|
| |
Changing the sieve in 0536fe92 changed which primes we generate
|
|
|
|
|
|
| |
It looks like Travis has some old version of Python 3 which can't handle
interpolating an integer into a byte string -- expr b"wtf %d" % (5)
fails with whatever is on Travis, but works fine in Python 3.7
|
|
|
|
|
| |
Suddenly installing python3-pip is broken, and I don't care enough to
dig deeper. Can probably come back when we switch to Xenial.
|
| |
|
| |
|
|
|
|
| |
Would have detected #1700 before release.
|
| |
|
|
|
|
| |
Closes GH #1557
|
| |
|
|\ |
|
| |
| |
| |
| | |
This is a contribution of Ribose Inc (@riboseinc)
|
|/
|
|
| |
See https://github.com/sphinx-doc/sphinx/issues/5417
|
|\ |
|
| | |
|
| | |
|