You are reading a single comment by @Gordon and its replies. Click here to read the full conversation.
  • Hi! I'd mentioned on Patreon a while back that when I hit $500/month I'd start hosting something that tested real hardware for every commit to the main Espruino project.

    We hit that goal in November, but with everything going on with the Bangle.js 2 KickStarter I didn't manage to get time to work on in properly, but hopefully in the next month or so I'll have time to get something live.

    Several years ago I did have a hardware testing system, and it just wrote the results of all the tests into a directory for the commit, then just scanned that to come up with a CSV file which could be viewed with a simple HTML graph webpage showing things like test fails, benchmark results.

    However that wasn't ideal (it was very hard to actually analyse that data to eg. find out which commit made the firmware larger or slower). So it brings up some questions....

    • Is there a better way to store/display the data from these tests?
    • Can we integrate with GitHub somehow (a bit like is done with Travis) so we can see the build status of a commit?

    Any thoughts? Ideally I don't want to have to host a bunch of databases, but there must be something that works statically (we're only talking of 1000s of datapoints, not millions).



Avatar for Gordon @Gordon started