Proposal for improving throughput for regression test

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi All,

As we all know, our regression tests are killing us. An average, one
regression will take approximately two and half hours to complete the
run. So i guess this is the right time to think about enhancing our
regression.

Proposal 1:

Create a new option for the daemons to specify that it is running as
test mode, then we can skip fsync calls used for data durability.

Proposal 2:

Use ip address instead of host name, because it takes some good amount
of time to resolve from host name, and even some times causes spurious
failure.


Proposal 3:
Each component has a lot of .t files and there is redundancy in tests,
We can do a rework to reduce the .t files and make less number of tests
that covers unit testing for a component , and run regression runs once
in a day (nightly) .

Please provide your inputs for the proposed ideas , and feel free to add
a new idea.

Thanks
Rafi KC
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux