![]() ![]() More significantly, I'd also propose that we turn on gating on openQA Pushed 'stable' almost immediately on creation, regardless of the (and unless the update was gated by a CI test, or somehow otherwiseĬonfigured not to be pushed automatically, updates would continue to be The Automated Tests tab in Bodhi, but they would be only informational So, I'd like to propose that we enable Rawhide update testing on the Low, enough that my current regime of checking the test results dailyĪnd restarting failed ones that don't seem to indicate a real bug On the whole, the level of false failures is (I would say) acceptably operations timing out that usually don't otherwise time out), but ![]() Occasional failures which seem to be related to Rawhide kernel slowness Of commission (we're using it to investigate a bug). One out of three worker systems for the stg instance is currently out The workers seem to keep up with the test load, even though So far this has been going more smoothly than I anticipated, ifĪnything. Resources we have are sufficient for the extra load. We run into unexpected failures or problems, and whether the hardware This was to see how smoothly the tests run, how often Smoothly now, and openQA respects Bodhi's "re-run tests" button soĪ few weeks ago, I enabled testing of Rawhide updates in the openQA When we first enabled gating - Bodhi's gating status updates work more This is going quite well, and I think we addressed the issues reported We've had openQA testing of updates for stable and branched releases,Īnd gating based on those tests, enabled for a while now. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |