rosenbrockc / ci Goto Github PK

The script ci.py has a switch for switching to verbose output mode. However, none of the functions coded so far support any level of verbosity. This is something that isn't critical at this point, but would be nice to have for debugging other user's installations (really, any respectable code has verbose output).

It would be useful to have the CI server be able to return the URL to a shield to post on the README page of a repo being monitored (like Travis and all of the others do). This is easy using:

https://img.shields.io/badge/Test%20Coverage-100-green.svg

We just need to have the latest scores written to JSON and then deserialized by the web page to return the URL with the appropriate fields replaced. Probably we would need to add one option to the config file that specifies the command to run on the repo's master to get the coverage etc. and the latest test scores.

Hi @rosenbrockc

So this is a bit weird, but i am developing a python application and strangely enough, i called it Py-CI.
I noticed you are the owner of that project name on PyPi.

Is there any chance we can discuss about maybe giving the ownership for that project to me?

Much obliged.

👍

The initial CI server is almost ready. However, I just realized that we need to discuss one more aspect. So far, I programmed the server to keep track of the output from stdout when running each unit test. That output is kept in memory until the wiki page with the unit test details is created. My original idea was to upload the contents of stdout for each test to a file on the wiki and then just link to it from the test results page.

That still seems like a viable possibility except that for some of the unit tests the output can be quite large. Do we place limitations on the size of the files we want to upload? If fortpy handles the unit testing, it provides summary information and will write out compilation errors or warnings and that output is usually small. But what about output from other programs? For example, the Wang Landau in UNCLE once produced a file that was 135GB!

Question: if the files are larger than 1MB, do we upload only part of them? If so, which part? If not, do we just say the file was too big? Do we remove it from the server then, or move it to some archive?

The default (current) implementation only allows the unit tests to be run in parallel with the multiprocessing module. However, the global settings allow for serial processing. It is implemented in the ci.py script, but not in the pyci.server module.

Although the repo settings allow for a timeout to be specified (after which any unit tests still running are forcible terminated), the pyci.server module currently doesn't implement this except in analyzing the run times returned in the execution statistics. The process termination still needs to be implemented.