Dear Avocado-VT Users,
This is a deprecation notice for the "jeos-21-64.qcow2" image.
The "jeos-23-64.qcow2", based on Fedora 23, has been available for quite
some time now, and instead of carrying such an old version on our pretty
limited storage space, we plan to:
* Change the compression for
Hello guys,
Dne 20.2.2017 v 14:46 Andrei Stepanov napsal(a):
It depends.
There could be a scenario where necessary to run ~ 200 tests at once.
If first bad-by-design test forgets/failed to cleanup, then some
sequential tests also will fail.
It is a question about usability.
I don't agree the `
Now that of course doesn't solve the problem I had with
scylla-cluster-tests, since the resources being used are external to the
machine executing tests. For cases like that, I'm afraid only good test
development practices can help.
On Mon, Feb 20, 2017 at 3:21 PM Lucas Meneghel Rodrigues
wrote:
On Mon, Feb 20, 2017 at 3:10 PM Cleber Rosa wrote:
>
> On 02/20/2017 08:46 AM, Andrei Stepanov wrote:
> > It depends.
> >
> > There could be a scenario where necessary to run ~ 200 tests at once.
> > If first bad-by-design test forgets/failed to cleanup, then some
> > sequential tests also will f
As an example, I wrote scylla-cluster-tests
https://github.com/scylladb/scylla-cluster-tests/
This test suite creates instances and storages on cloud providers, such as
AWS. Those resources cost money, so making sure stray instances are
properly terminated is paramount. There are cleanup procedur
On 02/20/2017 08:46 AM, Andrei Stepanov wrote:
> It depends.
>
> There could be a scenario where necessary to run ~ 200 tests at once.
> If first bad-by-design test forgets/failed to cleanup, then some
> sequential tests also will fail.
> It is a question about usability.
>
Andrei,
I've perso
On 02/20/2017 07:13 AM, Andrei Stepanov wrote:
> Hi
>
> Cleber, I think your example is not completely correct. You use "jobs".
> Bash/csh/zsh jobs is another topic. Your example is about bash jobs.
> Let's take a look a level up:
>
> 1. open xterm/gnome-terminal.
> 2. Run + put it in backgro
It depends.
There could be a scenario where necessary to run ~ 200 tests at once.
If first bad-by-design test forgets/failed to cleanup, then some sequential
tests also will fail.
It is a question about usability.
Okay, Radek, it seems that we should carefully write our tests, and kill
children
Still, Cleber's point is valid and coincides with my view. If you create a
subprocess that runs in the background, then you should keep track of it
and reap it in the cleanup procedures.
On Mon, Feb 20, 2017 at 1:13 PM Andrei Stepanov wrote:
> Hi
>
> Cleber, I think your example is not completel
Hi
Cleber, I think your example is not completely correct. You use "jobs".
Bash/csh/zsh jobs is another topic. Your example is about bash jobs.
Let's take a look a level up:
1. open xterm/gnome-terminal.
2. Run + put it in background: sleep 600 &
3. Close the terminal.
4. Check for processes. sl
Hey guys,
I think the following experiment can be didactic:
$ echo $$
1000
$ /bin/bash
$ echo $$
1010
$ sleep 600 &
$ exit
$ echo $$
1000
$ ps -eo ppid,cmd | grep sleep
1 sleep 600
We can say that shell with PID 1000 is Avocado, PID 1010 is your test
process, and sleep is the subproce
11 matches
Mail list logo
