Age | Commit message (Collapse) | Author |
|
Add unit tests for existing code in the test data creation library ahead
of a patch adding support for version 2 of the LNT JSON report file
format to ensure no existing code is broken in the process.
Differential Revision: https://reviews.llvm.org/D65747
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@368642 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Differential Revision: https://reviews.llvm.org/D65750
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@367924 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
As per PEP-008, wrap comments and docstrings in the test data creation
library at 72 characters.
Differential Revision: https://reviews.llvm.org/D65749
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@367923 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
There were are at least 3 issues when combining --pgo with
--exec-multisample:
* Make clean was not called between a measurement run and the next
profiling run.
* Make all was only called on the first measurement run.
* Cmake variable TEST_SUITE_PROFILE_USE=OFF was not set on the
second and later profiling runs.
These 3 issues are fixed by this patch.
It is also questionable whether we need to run profile collection
multiple times. With the instrumentation-based profile collection, the
profiles should be deterministic between different runs, and hence there
is no value in collecting profiles multiple times.
However, if in the future there would also be support for collecting
profiles e.g. based on performance counter sampling, the profiles might
be non-deterministic in such a scenario and having multiple profiling
runs could make a lot more sense. I'm leaving that discussion for
another time.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@365196 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Patch by Lily He
Differential Revision: https://reviews.llvm.org/D61662
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@362787 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
See r351631 to LLVM which installed the new license and developer policy for
subsequent contributions.
Note that I've left odd formatting and other idiosyncracies of the legacy
license structure text alone to make the diff easier to read. Critically, note
that we do not in any case *remove* the old license notice or terms, as that
remains necessary until we finish the relicensing process.
We understand that people may be surprised that we're moving the header
entirely to discuss the new license. We checked this carefully with the
Foundation's lawyer and we believe this is the correct approach.
Essentially, all code in the project is now made available by the LLVM project
under our new license, so you will see that the license headers include that
license only. Some of our contributors have contributed code under our old
license, and accordingly, we have retained a copy of our old license notice in
the top-level files in each project and repository.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@351654 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Forgot to include them in the previous commit
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@350706 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Fixes ValueError('need more than 0 values to unpack',) that
could appear in some corner cases when viewing results (the fewer
runs you have in your db the more likely you'll encounter it).
Differential revision: https://reviews.llvm.org/D56133
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@350704 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@350699 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349791 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349790 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
they are everywhere in the code
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349789 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Most of this code was written long ago before good linters were around.
Remove unused code, and fix poorly formatted.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349788 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349787 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349786 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349785 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349594 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349593 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349592 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349591 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349590 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349589 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349588 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349587 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349586 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349584 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349583 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349582 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
These were all valid style or correctness issues.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349579 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
When we commit we expire all objects in the session, meaning the will be
lazy loaded again next time they are accessed. Move the commit of all
found regressions to the end of processing, so the caches stay valid for
the entire life of analysis.
Also, use FieldChange directly for analysis, instead of RegressionInd,
we were mostly only accessing the change field anyways.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349578 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Linters help a lot of Python; however, we have so many issues in LNT we
can't use flake8. Start a whitelist of file to make sure are lint free
and make tox error on those.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349577 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Each add has to stage a sample, which leads to a SQL query and DB round
trip. For runs with a lot of sample, that can be avoided by adding them
all in one batch.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349576 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Looks like this cache is holding stuff between sessions. Since those
object could expire, lets purge the cache before we start.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349575 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
If any of these are false, we are returning false, so no point in
checking the rest of them. This make regression evolution MUCH faster.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349574 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
This is certainly a programming error of some sort.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349220 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
This set of queries were taking a long time. Make the query faster,
by using .first(), and then cache the results in our testsuitedb.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349219 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Hooks were not being loaded when importing from the command line. Since
they contain data processing rules, we should have them loaded!
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349218 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349116 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
Tox is really handy for building a venv and running all the tests and
qualification tasks in a repeatable way.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349114 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349113 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349112 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349111 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
This is good testing for lit, and will make sure we don't get stuck
in an old version.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349110 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349109 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349108 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349107 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349106 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349105 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
I had not seen this test fail, because of other infrastructure issues.
Simple refactoring to move the query to the outside of the function
under test.
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349104 91177308-0d34-0410-b5e6-96231b3b80d8
|
|
git-svn-id: https://llvm.org/svn/llvm-project/lnt/trunk@349103 91177308-0d34-0410-b5e6-96231b3b80d8
|