| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | show current test number | Joey Hess | 2013-11-20 |
| | | |||
| * | remove fsck tryharder code | Joey Hess | 2013-11-20 |
| | | | | | | | It turned out to be broken, and led to failures. 6d67245728bbbc07ad1eeaf5b3c49f64c6bbcd11 was a better fix for the problem that code tried to fix. | ||
| * | fix failure propigation | Joey Hess | 2013-11-20 |
| | | |||
| * | try to recover even if git fsck cannot be coaxed to tell us any bad objects | Joey Hess | 2013-11-20 |
| | | | | | | | | Sometimes git fsck outputs no shas even with --verbose, but fails, due to badly corrupt objects. The best thing to do in this situation is to try to pull and rsync from remotes, hoping that the bad objects will be overwritten. | ||
| * | improve test runner | Joey Hess | 2013-11-20 |
| | | |||
| * | retrying | Joey Hess | 2013-11-19 |
| | | |||
| * | run a fsck at end to double-check | Joey Hess | 2013-11-19 |
| | | |||
| * | fix corruption of origin repo | Joey Hess | 2013-11-19 |
| | | |||
| * | initial work on git repository destroyer | Joey Hess | 2013-11-19 |
| I suspect this might sometimes corrupt the **source** repo, so use with caution! | |||
 |
index : git-repair | |
| [no description] | git repository hosting |
| summaryrefslogtreecommitdiff |
path: root/test-runner.hs