Re: making test suites work the same way

On Mon, Feb 6, 2017 at 1:35 PM, Kamil Paral wrote: > > That's a good point. But do we have a good alternative here? If we depend > on packages like that, I see only two options: > > a) ask the person to install pyfoo as an RPM (in readme) > b) ask the person to install gcc and

Re: making test suites work the same way

> Well, after more discussions with kparal, we are still unsure about the > "right" way to tackle this. > Our current call would be: > 1) sync requirements.txt versions with fedora (mostly done) > 2) allow --system-site-packages in the test_env > 3) do `pip install -r requirements.txt` (with

Lift type-restriction on ibtaskotron's cli + resultsdb directive

Hey Gang, this is bugging me for quite a while now, and although I know why we put the restrictions there back then, I'm not sure the benefits still outweigh the problems. Especially now, when we'll probably be getting some traction, I'd like to propose removing the type-check completely. On top

Libtaskotron - allow non-cli data input

Chaps, we were discussing this many times in the past, and as with the type-restriction, I think this is the right time to get this done, actually. It sure ties to the fact, that I'm trying to put together Taskotron-continuously-testing-Taskotron together - the idea here being that on each