ceph / paddles

RESTful API to store (and report) on Ceph tests

ceph/paddles Issues

Bug: "unknown" status of runs and jobs
Updated 3 months ago
[Bug]: We should create a file "/run/secrets/paddles_sqlalchemy_url" to use postgresql, or we will use sqlite directly.
Updated 2 years ago
Unknown license for paddles
Updated 4 years ago
Use travis for running linter and unittests
Updated 5 years ago
ERROR:teuthology.report:Could not report results to
Closed 6 years ago2
Step 15, Message of "No handlers could be found for logger "sqlalchemy.engine.base.Engine"
Updated 8 years ago5
worked as lock_server and result_server，only support concurrent job <5
Updated 9 years ago1
Add Run.user and Run.machine_type columns
Closed 10 years ago1
Ability to query runs and jobs by status
Closed 10 years ago2
Provide an API grouping runs by suite
Closed 10 years ago
Add offset parameters to requests that accept count parameters
Updated 11 years ago
Update documentation
Updated 11 years ago
Add Job.failure_reason and alembic migration
Closed 11 years ago
Provide more information about run/job timing
Closed 11 years ago2
runs should have the `timestamp` key in `__json__`
Closed 11 years ago4
enable querying of `runs`
Closed 11 years ago5