Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

This page tracks ideas for improving the stability and throughput of the DAOS CI system.  This just supplements Jira for communication & progress reporting purposes. 

All the individual improvement ideas are tracked in Jira epic DAOS-3929.


Ticket(s)TaskStatusResult

DAOS-3914

CORCI-840

Increase throughput on HW clusters by running multiple servers per HW node and split one of the HW clusters.blockedWait for new HW.
CORCI-841Build new HW clusters and get them into CI as soon as HW shows upblockedHW ships 1/22
DAOS-3915Analyze HW tests to see if they can be moved to weekly and to understand if different cluster combos would helpDone

Splitting clusters from 8 to 4 node will no make an

immediate substantial impact.  This is going to help 

long term though, particularly when adding the new 

hardware.

CORCI-717Node failures are often the cause of intermittent CI issues but need console log to debugtodo
CORCI-842PDT presentation on commit message pragmas, use of quickbuildtodo
DAOS-3868Fix quickbuild issues, this will allow short-circuit of time consuming build operations when appropriatetodo
CORCI-711HW nodes are provisioned from snapshot, fix out-of-space and other cruft issues that cause intermittent failuresin-progress

DAOS-3607

DAOS-2759

Increase flexibility to run different groupings of tests by running from RPMsin-progress
CORCI-843If a change impacts files in the "doc" directory then skip unnecessary build/test cycles.todo
DAOS-3921Reduce wait time in daos_test rebuild subtestsin-progress
DAOS-3919Reduce IorSmall runtimes by eliminating uninteresting mux combintations and unnecessary formattingDone~50 minute reduction?
DAOS-3930IorSmall runtimes are all over the maptodo
CORCI-831Old PRs can use wrong packagesDoneReduced intermittent failures 
DAOS-3840Use OPA adapters not ethernet in CIDoneModest improvement, but not what expected.


The primary metric for tracking improvements is total hours master jobs take to complete.  Total time includes waiting time plus run time.  The chart below includes randomly select successful runs against master.


  • No labels