summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Added LGPL license fileHEADmasterJo Asplin2012-03-281-0/+504
|
* Updated README + misc fixes/cleanupJo Asplin2011-09-206-99/+173
|
* Fixed commentJo Asplin2011-08-121-1/+1
|
* Improved labels.jasplin2011-05-272-15/+9
|
* Removed obsolete comments.jasplin2011-05-271-6/+2
|
* Cleaned up labelsjasplin2011-05-274-3/+6
|
* Refactored test case filter feature to increase code reuse.jasplin2011-05-276-158/+159
|
* Removed trailing whitespace.jasplin2011-05-261-1/+1
|
* Added Top Changes page to replace ranking feature.jasplin2011-05-2630-1843/+1776
| | | | | | | | | | | | This commit introduces the Top Changes page. This page retrieves 'top 10' changes for all host/platform/branch combinations from a new 'change' database table. The script that updates this table for a given host/platform/branch combination is run automatically after uploading a new set of results (since this is when new changes may potentially arise). This commit also removes the ranking feature as this is obsoleted (more or less) by the new feature.
* Added skeleton for Change Summary pagejasplin2011-05-0454-74/+430
|
* Fixed indexing bug in time series plot containing invalid results.jasplin2011-04-261-27/+41
| | | | | | | Selecting a snapshot in the time series plot did not have the expected effect if certain other snapshots did not have a valid median result (because all results were invalid or missing altogether).
* Adjust formula for last change stability score.jasplin2011-04-136-29/+29
| | | | | | | | | | | | | | | | | | The formulas for LCSS and LCSS1 are now back to the original: LCSS1 = LCMS * LCGSS * LCLSS * LCDS1 LCSS = LCSS1 * LCDS2 A simple product turned out to be the most robust way to avoid assigning significant scores to certain outlier cases after all. This patch also redefines the global separation score slightly to make it more robust (the values before the last change are now compared against all values at or after the last change, rather than just the last change value itself). Finally, the default maximum durability score is adjusted from 30 to 10 (i.e. 10 seems to be sufficient to establish stability).
* Adjust formula for last change stability score.jasplin2011-04-123-3/+3
| | | | | | | | | | | | | The formula for LCSS is adjusted from LCSS = (LCMS + LCGSS + LCLSS + LCDS1 + LCDS2) / 5.0 to LCSS = (LCMS + LCGSS + LCLSS + (LCDS1 * LCDS2)) / 4.0 This ensures that certain outlier cases are not falsely given a significant score.
* Prepared for change summary page; added navigation links.jasplin2011-04-1263-4/+108
|
* Merge branch 'master' of scm.dev.nokia.troll.no:bm/jasplins-bm2jasplin2011-04-051-2/+2
|\
| * BM2: Use `/home/qt/benchmarks' directory instead of the `benchmarks2'Sergio Ahumada2011-04-011-2/+2
| | | | | | | | We want to track the Tieto benchmarks files as well.
* | Bugfix: Failed verification assumed data-driven testing.jasplin2011-04-051-1/+9
|/ | | | | | | | | | | | QCOMPARE and friends could be used to ensure that performance was measured for the intended code path: A failed verification step would indicate an invalid benchmark result. This information would then be stored in the database and taken into consideration in a later analysis. The feature falsely relied on explicit data tags being used and was simply ignored for test functions without such tags (i.e. without a corresponding _data() function).
* Added --remote option.jasplin2011-03-301-37/+62
| | | | | | | | | | | The --remote option allows the upload script to be run either on gitestr (remote = 0) or on another host (remote = 1). When running on gitestr, 'cp' will be used instead of 'scp' etc. The reason we need this is that scp to gitestr currently doesn't work when the script is run in gitestr itself (the command is trying to access another (apparently unrelated) host for some reason).
* Keep repo with 'testable snapshots' file away from externals.jasplin2011-03-301-15/+42
|
* Merge branch 'master' of scm.dev.nokia.troll.no:bm/jasplins-bm2jasplin2011-03-291-13/+19
|\
| * BM2: Improve robustness of bm2_result_watcher.plSergio Ahumada2011-03-211-0/+1
| | | | | | | | | | | | Now we are compressing the backup files Task-number: QTQAINFRA-40
| * BM2: Improve robustness of bm2_result_watcher.plSergio Ahumada2011-03-181-13/+18
| | | | | | | | Task-number: QTQAINFRA-40
* | Update a 'testable snapshots' file on each upload.jasplin2011-03-291-1/+85
|/ | | | | | | | | | | | | | This patch causes the upload script to update a a 'testable snapshots' file (located at qt@gitestr.nokia.troll.no:bmtestable/bmtestable.xml) each time a new set of results is successfully uploaded to the database. This file indicates the most recent tested snapshot (SHA-1) in each branch. The file can be inspected by external testers (like Tieto) to ensure they test a subset of the snapshots tested locally. This property can be important for certain analyses.
* Output to stdout/stderr and use exit codes in a consistent way.jasplin2011-03-182-79/+85
|
* Make SQL queries safer and more robust.jasplin2011-03-1815-177/+177
| | | | | | | | | | | | | | | | | | | | | | | This patch ensures proper processing of SQL queries by making use of the second argument to the Psycopg execute() method: WRONG: >>> SQL = "INSERT INTO authors (name) VALUES ('%s');" # NEVER DO THIS >>> data = ("O'Reilly", ) >>> cur.execute(SQL % data) # THIS WILL FAIL MISERABLY CORRECT: >>> SQL = "INSERT INTO authors (name) VALUES (%s);" # Notice: no quotes >>> data = ("O'Reilly", ) >>> cur.execute(SQL, data) # Notice: no % operator This has a double purpose: 1: Arguments are automatically handled properly according to their type (in particular strings containing single quotes). 2: SQL injection is prevented.
* Added diagnostic messages and an extra completeness check.jasplin2011-03-111-18/+68
|
* Let uploadresults.py execute computerankings.py itself as appropriate.jasplin2011-03-102-19/+112
|
* Corrected typo.jasplin2011-03-041-1/+1
|
* Define LCSS as a sum instead of a product.jasplin2011-03-033-7/+7
|
* Merge branch 'master' of scm.dev.nokia.troll.no:bm/jasplins-bm2jasplin2011-03-011-10/+3
|\
| * BM2: First attempt to Arrange for Benchmark RankingsSergio Ahumada2011-02-281-10/+3
| | | | | | | | | | | | Using the new uploadresults.py script Task-number: QTQAINFRA-50
* | Fixed bug: ensure proper radio button grouping.jasplin2011-03-011-1/+1
|/
* Minor.jasplin2011-02-241-1/+1
|
* Prevent uploading results when affected rankings exist.jasplin2011-02-243-29/+63
| | | | | | | | | | | | Reject uploading if rankings exist for the given context, since that would require a recomputation of these rankings. Note that this check if sufficient as long as we assume that results are uploaded in an order that is consistent with the order of the corresponding SHA-1s in the branch in question (i.e. that results will never be uploaded for a SHA-1 that precedes (is "older" than) a SHA-1 for which results already exist). This assumption ensures that results for a new SHA-1 will not alter the input for any existing ranking.
* Minor cleanup.jasplin2011-02-244-8/+25
|
* Comment out 'forced' flag.jasplin2011-02-241-1/+1
|
* Cleaned up handling of command-line args ++.jasplin2011-02-245-196/+240
| | | | | | This commit adds optional dbhost and dbport args to the command line in order to use other database servers than the default.
* Fixed bug.jasplin2011-02-242-4/+4
| | | | | | | | | When computing the quality score for a time series, an invalid LSD or MDRSE (indicated by -1) should contribute a max quality score since each of them _normally_ arises when analyzing a time series that is very short, and thus not really qualifying as being of "poor quality" yet.
* Fixed bug that caused zero-division for small sets.jasplin2011-02-241-1/+2
| | | | Fix it properly this time ;)
* Revert "Fixed bug that caused zero-division for small sets."jasplin2011-02-241-2/+1
| | | | This reverts commit 485ea014cb49073fa86c6884c62136cfc56cc34f.
* Fixed bug that caused zero-division for small sets.jasplin2011-02-241-1/+2
|
* Remove timestamp argument from command line.jasplin2011-02-231-17/+5
| | | | | | | | | | | | | | | | | | The timestamp command-line argument is obsolete (and has probably always been!), so it is removed. Ordering is currently based on the assumption that results are uploaded in the order the associated SHA-1s occur in the branch. In other words: once results for a given SHA-1 are uploaded, it is assummed that results for older SHA-1s will not be uploaded. Should this become too restrictive at some point, we can let the server figure out the SHA-1 ordering (e.g. by analyzing a local repository clone of the branch in question). The client would still only pass the SHA-1 itself.
* Replaced certain checkboxes with radio buttons.jasplin2011-02-235-48/+22
|
* Adjust main page title.jasplin2011-02-181-1/+1
|
* Show "ranked snapshots only" in main page title when applicable.jasplin2011-02-182-1/+3
|
* Fixed bug.jasplin2011-02-181-4/+7
|
* Added basic annotation.jasplin2011-02-1810-27/+260
| | | | | | | | | | On the rankings page, a note for an individual benchmark can now be edited. This is the first step towards a more sophisticated annotation concept. It could for example be useful to interactively classify a benchmark as "suspended" or "active".
* Replaced some acronyms with more informative text.jasplin2011-02-171-5/+9
|
* Use infinite endpoint for snapshot interval in single time series URL.jasplin2011-02-163-13/+32
| | | | | | | | The URL that refers to a single time series now specifies an infinite enpoint for the second snapshot (by specifying an invalid SHA-1). Reloading the page is then guaranteed to show the latest available results, This is likely to be more useful in practice.
* Enable interactive sorting on ranking pos delta.jasplin2011-02-161-2/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-08 16:17:18 +0000