[CentOS-devel] Testing Nightly and Status Board
22t at tripolho.com
Wed Mar 13 17:29:26 UTC 2013
I have been seeing a lot of weird things happening lately, I mean, after
the 500-more package update.
After the last updates a Centos 6.3 32-bit virtual machine running under
virtual box 4.2.8 does not boot anymore.
I have just updated my workstation to "Linux version
2.6.32-358.2.1.el6.x86_64 (mockbuild at c6b8.bsys.dev.centos.org) (gcc
version 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC) ) #1 SMP Wed Mar 13
00:26:49 UTC 2013" and it unexpectedly locked when I started Thunderbird
(there was a VM running under Virtualbox when I did it).
CTRL-ALT-BACKSPACE apparently completed the "locking job".
Are you noticing that too?
On 03/13/2013 01:09 PM, Karanbir Singh wrote:
> At the moment, we run tests on a nightly basis, only in kvm vm's and the
> results dont go very far. I'd like to propose we use the entire QA
> bladecenter and run the entire compliment of deploys and tests, then
> post them in a status board which has some history ( stashboard ? )
> Going one step further, we should run the entire t_functional tests as
> well as start incorporating some of the, now stale, t_external tests.
> At the moment we do deploys over http and nfs, to local and remote
> storage, under Xen, KVM, bare-metal and some virtualbox and some vmware
> hypervisors, for i386 and x86_64.
> I had a brief chat with Fabian about this yesterday, and we both think
> its doable, in the short term. Anyone else have thoughts about this ? or
> want to propose reporting mechanisms that might be better in line with
> the intended result : to give people a single perspective on the state
> of things, as a confidence point. And also to allow people to easily add
> tests that are then run nightly, so they can address their own corner cases.
More information about the CentOS-devel