Skip to content

Merge latest codespeed/master from upstream into speed.pypy.org - #1

Merged
ewdurbin merged 537 commits into
python:speed.pypy.orgfrom
mattip:speed.pypy.org
Apr 8, 2019
Merged

Merge latest codespeed/master from upstream into speed.pypy.org #1
ewdurbin merged 537 commits into
python:speed.pypy.orgfrom
mattip:speed.pypy.org

Conversation

@mattip

@mattipmattip commented Apr 3, 2019

Copy link
Copy Markdown

I tried this out locally to iron out the fine points. Major breaking changes from the existing site:

  • the module has moved from example to sample_project
    • are there files in example that still need to move (like wsgi.py`)?
  • should I copy all the sample_project to example so we do not have to change deployment recipes? Speed.python.org uses neither.
  • the database model is too different, migration on top of the old db fails
    • however manage.py dumpdata > cleanup > manage.py loaddata works. I have a file of the middle stage ready to go
    • this means we need to change the table names or drop the existing tables

nomeataand others added 30 commits July 19, 2014 18:42
@nomeata
New admin action for Reports: recalculate
94ee71a
After doing a bulk upload of benchmarks, possibly not in chronological
order, the reports might show changes wrt. to the wrong previous commit.
Then, triggering this action for all reports helps.
@nomeata
Aggregate report per unit_title, not per unit
bb4e36b
If we have several very different things (Buildtime vs. Runtime) with
the same unit (seconds), we want to keep them separate.
@nomeata
Bugfix: Changes view for old revisions
e66808d
This fixestobami#168.
@nomeata
Also include values "0" in the reports
11c30b4
If no value is reported, then there wouldn't be a Result object, so a
value of 0 is valid.
@tobami
Merge pull requesttobami#169from nomeata/submit
0f16149
My upstreamable changes so far
Closestobami#168
@nomeata
Support for +∞ and -100% in change columns
0d27299
This fixestobami#170.
@nomeata
Fix 0/0=0 in change column
31a4639
@nomeata
Implement “latest significant results” table and feed
248fb36
This fixestobami#171
@nomeata
Refactor feed generation a bit
9014aa6
@nomeata
Fill the RSS feeds with a bit more content
c657ee6
Especially the summary is useful
@nomeata
Include the full changes table in the feed
424e304
(by putting it into a template of its own)
@nomeata
New color "light green" for positive trends
0d8f6ae
to distinguish them from non-trend improvements.
@nomeata
Simplify classification logic for the summaries
2538ca7
(changes results before trends, averages before individual results)
@nomeata
Integrate code review
8eda931
@tobami
Merge pull requesttobami#172from nomeata/submit
e85114c
Two more changes
@tobami
Add test for reports view
471b2dc
@tobami
Use require_GET decorator to disallow non-GET requests
3b1c5dc
@nomeata
Remove @require_GET from getcommitlog
b732cd6
As it is not a view. Fixestobami#175.
@tobami
Merge pull requesttobami#177from nomeata/submit
82ff7d3
Remove @require_GET from getcommitlog
@tobami
Add filters to admin models.Fixestobami#179
1bc316f
@tobami
Add plural name for Branch model
38eaa73
@kmod
codespeed doesn't work with Django 1.7
47b50a7
@tobami
Merge pull requesttobami#180from kmod/master
b33a60c
codespeed doesn't work with Django 1.7
@tobami
Show better error message when no project has track=True
b9f57e4
@tobami
Default to track=True for new projects
ccb422e
@tobami
Fix executable admin search field.Fixestobami#139
fa5c6aa
@tobami
Merge pull requesttobami#184from tobami/default-proj-error
d8d1a6c
Default proj error
@thedavecollins
Correct install_requires to match requirements.txt
f91ab12
@tobami
Merge pull requesttobami#185from thedavecollins/master
d79cb96
Correct install_requires to match requirements.txt
@pepsiman
Get mercurial logs for non-default branches
7cd9dc2
syrusakbaryand others added 15 commits March 28, 2019 22:45
@syrusakbary
Fixed python 3 compatibility in github integration
ce8cac3
@tobami
Merge pull requesttobami#266from wasmerio/patch-1
079824c
Fixed python 3 compatibility in github integration
@tobami
Rename extra_body into extra_script
17521a7
@tobami
Fix branch queries not using get
1a17893
@tobami
Use newer MIDDLEWARE setting for Django 2.0+ compat
752e9d1
@tobami
Merge pull requesttobami#267from tobami/use-newer-middleware-settings
d513ef7
Use newer middleware settings
@tobami
Add new historical data view
1480a47
- Re-implement home page using a class view and add settings-based context
@tobami
Implement historical graphs on home page
b2dab52
- Based on PyPy's branch
@tobami
Merge pull requesttobami#268from tobami/historical-home
a741922
Historical plots in the home page
@tobami
Document home page settings
d225889
- Formatting improvements
@tobami
Update testdata with more complete results
c439b8f
@tobami
Merge pull requesttobami#269from tobami/document-historical-plots
46a3dd5
Document historical plots
@mattip
merge default into branch
e411982
@mattip
fix merge and update
984b0d8
@mattip
ENH: handle environment for historical data
ba2fd71
@mattipmattip added the enhancement New feature or request label Apr 3, 2019
@vstinner

vstinner commented Apr 5, 2019

Copy link
Copy Markdown
Member

Sorry I don't understand which project is the upstream now. Why are there 3 GitHub projects?

If https://github.com/mattip/codespeed is the upstream, why not just remove this one for example?

@mattip

mattip commented Apr 5, 2019

Copy link
Copy Markdown
Author

Upstream is the generic tobami/codespeed. This one should be the python fork used to deploy the two websites.

@ewdurbin

ewdurbin commented Apr 8, 2019

Copy link
Copy Markdown
Member
  • the module has moved from example to sample_project

Probably a good idea to name the module speed_pypy similar to how the speed.python.org branch is setup.

  • are there files in example that still need to move (like wsgi.py`)?

Not that I'm aware of, wsgi.py is there to give an entry point for gunicorn.

  • should I copy all the sample_project to example so we do not have to change deployment recipes? Speed.python.org uses neither.

No, we can update the app entrypoint.

  • however manage.py dumpdata > cleanup > manage.py loaddata works. I have a file of the middle stage ready to go
  • this means we need to change the table names or drop the existing tables

This can be accommodated, though I'm not sure what cleanup is referencing here.

@mattip

mattip commented Apr 8, 2019

Copy link
Copy Markdown
Author

cleanup means I edited the json file to remove all the tables and information no longer relevant for the new data model. That file is ready to go

ewdurbin added a commit to python/psf-salt that referenced this pull request Apr 8, 2019
@ewdurbin
updates for speed.pypy.org, complimentpython/codespeed#1
08a8ae6
@ewdurbinewdurbin mentioned this pull request Apr 8, 2019
Merged
@ewdurbin

ewdurbin commented Apr 8, 2019

Copy link
Copy Markdown
Member

@mattip I opened the above ref'd PR to point to speed_pypy as the module. that and the addition of a wsgi.py are all I'm aware of that we need before merging them both.

@mattip

mattip commented Apr 8, 2019

Copy link
Copy Markdown
Author

added the wsgi.py from example and all the files from sample_project to speed_pypy

@ewdurbin
ewdurbin merged commit ffa154f into python:speed.pypy.orgApr 8, 2019
mattip pushed a commit to mattip/codespeed that referenced this pull request Oct 26, 2020
@0xflotus
Merge pull requestpython#1from 0xflotus/patch-1
fa8155a
fixed Additionally
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

enhancementNew feature or request

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

20 participants

@mattip@vstinner@ewdurbin@nomeata@tobami@kmod@thedavecollins@pepsiman@zware@str4d@javierhonduco@octmoraru@catalin-manciu@AlekSi@mwatts15@chriscool@smarr@quasilyte@Timmmm@Emil-G