| commit | 834733bbe5d7c5659e7252ac6842a1ba748f7dba | [log] [tgz] |
|---|---|---|
| author | Jan Kundrát <jkt@kde.org> | Fri Jun 12 01:50:40 2015 +0200 |
| committer | Jan Kundrát <jkt@kde.org> | Fri Jun 12 01:50:40 2015 +0200 |
| tree | 247eed34ec587cf6f1ce4cb544c4eae41e9e9d7b | |
| parent | f265245ccee20cb34e203ca238827e264bb441e0 [diff] |
Let scripts return some useful message about failure This patch exports a new env var for the script, the $TH_RESULT_FILE. If the launched script writes something into the file name specified in that env var and if the content of that file doesn't appear to indicate a successful build, the content of the file is used as summary message sent back to Zuul. Originally, this patch attempted to do a similar thing through reading back stuff from the shell's output log and reporting the last line from that output, but the two major disadvantages were the inclusion of timestamps in the log output, and Python's enrichment of the log line with timestamps. I pondered writing a custom Python's logging.Handler which simply remembers the last message, but the required changes in utils.execute_to_log appeared rather messy to my untrained eye. The main driver behind this change is a need to differentiate from hard build failures (where we don't get any build artifacts because the build simply failed) from "mere" test failures. Yes, our (KDE) tests are still sloppy, and we have a fair amount of broken test still around, which is why this difference matters to us. The result field in Zuul is more or less free-form, so this patch does not impose any restrictions about its format, except the "cannot start with 'SUCCESS'" because that one is indeed very, very special. It can be seen in action at http://ci-logs.kde.flaska.net/matrix.html . Change-Id: I48c29d2566da12b02dcf27a551a058ecc4a303d4
A set of CI tools.
worker_server.py is a worker server that loads and runs task_plugins.
Each task_plugin is a zuul gearman worker that implements, handles, executes a job, uploads/post-processes the logs and sends back the results to zuul.
gate_real_db_upgrade: Runs the db_sync migrations on each dataset available in the datasets subdir.