Open dcwhite opened 10 years ago
@benjaminlarson Add a comment with progress made below.
Some tests aren't being tested on all machines. The following spreadsheet shows which OS will perform which test. Builds should be up to date. Is there a way to streamline this checklist into a trello card? Such as using copy and paste?
Is the Trello board still useful, or should be just move to a Google spreadsheet?
I'm updating the boards now for module development actually. It's far superior to a spreadsheet, but I agree it's a pain to keep all these things in sync.
Would updating broken networks be another good job for Max?
Sure. Could you show him how to access all the test machines?
Sure - I gave him a quick tutorial a few months ago, but a refresher won't hurt.
Thanks! The known broken networks are:
@mhansen1 will continue working on this
Looks like no interns for a while, pushing this one.
Need to simplify Trello board
Testing issues will be grouped together better and we will have a big discussion on resource allocation.
When @allywarner is full-time Seg3d, we can get all the CIBC machines running builds and tests again for both SCIRun and Seg3d, so let's revisit this then.
Stale issue message
@jessdtate We do still need to organize all the testing processes better. Is Trello the way to go, or should we investigate some other tool?
This issue is stale because it has been open 120 days with no activity. Remove stale label or comment or this will be closed in 60 days.
This issue is stale because it has been open 240 days with no activity. Remove the stale label or comment, or this will be closed in 60 days.
This issue is stale because it has been open 240 days with no activity. Remove the stale label or comment, or this will be closed in 60 days.
https://trello.com/b/DqbtQrX7/scirun-5-broken-networks