Bug #16916
closed
Refactor Workbench 2 testing
Description
There are some strange failures:
to see more details please see
developer-tests-workbench2: #104 /console
The WB2 tests still run on the main CI server. Move this to a Jenkins Satellite, which means build a docker image. Will need some refactoring so we don't rebuild the world every time the tests run.
Updated by Ward Vandewege over 3 years ago
- Target version set to 2020-10-07 Sprint
- Assigned To set to Ward Vandewege
- Status changed from New to In Progress
The integration tests are failing, somewhere inside the
/root/go/bin/arvados-server boot -type test -config /tmp/workbench2/tools/arvados_config.yml -own-temporary-database -timeout 20mcommand. Perhaps some sort of race condition. It shouldn't have errored out in the cleanup function though, I've pushed a patch that resets the pipefail and error mode on the script in the cleanup function.
Updated by Ward Vandewege over 3 years ago
This test is running on the jenkins master. Todo: build a packer image and move it to the satellites.
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2020-10-07 Sprint to 2020-10-21 Sprint
Updated by Ward Vandewege over 3 years ago
- Description updated (diff)
- Subject changed from Workbench 2 cypress test fail before starting to Refactor Workbench 2 testing
Updated by Ward Vandewege over 3 years ago
- Target version changed from 2020-10-21 Sprint to 2020-11-04 Sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2020-11-04 Sprint to 2020-11-18
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2020-11-18 to 2020-12-02 Sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2020-12-02 Sprint to 2020-12-16 Sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2020-12-16 Sprint to 2021-01-06 Sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-01-06 Sprint to 2021-01-20 Sprint
Updated by Ward Vandewege over 3 years ago
As a first step, I'm moving these tests off to a Jenkins satellite. Packer image generation ready for review at commit:22d40663a3664b5f5e47d37c9b58a20165737c5c on branch 16916-move-wb2-tests-to-jenkins-satellites in the arvados-dev repository.
A build with this image ran at workbench2-run-tests: #591 . It has one error, which I can reproduce locally, so I assume that's a real bug.
Updated by Lucas Di Pentima over 3 years ago
Ok, I've read a little packer documentation and can say this LGTM. I'm not clear on how these provisioner scripts are called (I guess through google's platform) and if you need me to try this I should make my GCP account ready in terms of permission roles and such, but as you already tested it I suppose further testing isn't needed. :)
In summary, looks good to merge!
Updated by Ward Vandewege over 3 years ago
Lucas Di Pentima wrote:
Ok, I've read a little packer documentation and can say this LGTM. I'm not clear on how these provisioner scripts are called (I guess through google's platform) and if you need me to try this I should make my GCP account ready in terms of permission roles and such, but as you already tested it I suppose further testing isn't needed. :)
In summary, looks good to merge!
Thanks, will merge. I've added the corresponding Jenkins job to build the image; it's at https://ci.arvados.org/view/Packer%20Images/job/packer-build-jenkins-image-workbench2-tests/
Updated by Ward Vandewege over 3 years ago
- Status changed from In Progress to Resolved