38a906b0e1
`TZ='UTC'` is not a portable setting for the TZ environment variable. POSIX says you’re supposed to use something like `TZ='UTC0'` instead. Although `TZ='UTC'` works when GLIBC is used, this is not necessarily true on other POSIX platforms. [1][2] [1] http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20170918/009289.html [2] http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html#tag_08_03 Change-Id: I1dca0b84de0ec0af3a103e2cbbf731512eb59497 Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de> Reviewed-on: https://review.coreboot.org/21721 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net> Reviewed-by: Martin Roth <martinroth@google.com> |
||
---|---|---|
.. | ||
bucketize.sh | ||
foreword.wiki | ||
push-to-wiki.sh | ||
README | ||
status-to-wiki.sh | ||
towiki.sh |
Scripts to publish board-status data to the wiki ================================================ These scripts parse the board-status repository (and the coreboot repository as companion) to build a meaningful representation of the test coverage stored in board-status. The server runs these nightly (CET/CEST), so no user interaction with the wiki page is needed. How to use ---------- When modifying the scripts, or when publishing the results elsewhere, you might want to run them yourself. You'll need the board-status and the coreboot repository checked out side by side, named "board-status" and "coreboot" respectively (in particular without .git suffix). To emit wiki-text, in the board-status repository's top-level directory, run $ ../util/board_status/to-wiki/status-to-wiki.sh The output ends up on stdout, so you'll have to store it yourself, if you need it later. `push-to-wiki.sh FILENAME TITLE` can be used to push a file into the wiki. User credentials are looked up in ~/.wikiaccount, which should look like USERNAME=user USERPASS=password How it works ------------ status-to-wiki collects the reports and sorts them in buckets by report date. These can have weekly, monthly and quarterly granularity. It then passes these into the towiki script, which reads the data in more details and prints them in the output format. Contributions ------------- These scripts are rather bare, and you're welcome to extend them to extract more useful data from both repositories, and to present the data in a nicer way. A rewrite into another (reasonable) language is fine, too - shell quickly finds its limits for this kind of text processing.