incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rohit Yadav <bhais...@apache.org>
Subject Change in integration test for javelin
Date Sat, 26 Jan 2013 01:46:48 GMT
Because of this code in UserVmManagerImpl;

        String workers = configs.get("expunge.workers");
        int wrks = NumbersUtil.parseInt(workers, 10);

        String time = configs.get("expunge.interval");
        _expungeInterval = NumbersUtil.parseInt(time, 86400);
        if ( _expungeInterval < 600 ) {
         _expungeInterval = 600;
        }

If a expunge interval is < 600s, it's set to 600. For DevCloud the
interval is just 60s. Because of this, when running integration smoke
tests, it fails on the last test which is VM expunging. I've added the
same logic in integration smoke test:

commit bc40ed85e5c97dddd86ce6421feb50c7c92a54c8
Author: Rohit Yadav <bhaisaab@apache.org>
Date:   Fri Jan 25 17:42:04 2013 -0800

    test_vm_life_cycle: Fix expunging logic as in mgmt server
    Sets expunge interval to 600 if it's less than that

Status of javelin: all basic integration tests for DevCloud passes,
all build profiles are working including nonoss, mgmt server runs and
works for various api calls basic zone dogfooded against DevCloud.

Regards.

Mime
View raw message