-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
weaver: bump version to 5.6.0 #463
Conversation
…etry going +1 index
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2691/Result ❌ FAILURE BIRDHOUSE_DEPLOY_BRANCH : update-weaver DACCS_IAC_BRANCH : master DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-118.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1629/NOTEBOOK TEST RESULTS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean it all looks good to me but that same test cell is failing with the same problem. I don't really know what the cause could be for that.
@huard
Scratch all that. Input URL was invalid. |
@fmigneault we do have a |
Update: found the potential cause. Somewhere along the Weaver->CWL->WPS chain, either OWSLib or PyWPS inject an empty file for the
|
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2696/Result ❌ FAILURE BIRDHOUSE_DEPLOY_BRANCH : update-weaver DACCS_IAC_BRANCH : master DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-216.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1633/NOTEBOOK TEST RESULTS |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2697/Result ❌ FAILURE BIRDHOUSE_DEPLOY_BRANCH : update-weaver DACCS_IAC_BRANCH : master DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-216.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1632/NOTEBOOK TEST RESULTS |
OK, so Weaver's tests are working again now, but I'm getting new errors from GeoServer tests and the stress-test. @mishaschwartz @tlvu Any chance those errors are introduced by f252ee8 including latest birdhouse-deploy changes as well? |
Running build: http://daccs-jenkins.crim.ca/job/DACCS-iac-birdhouse/ to test (http://daccs-jenkins.crim.ca/job/PAVICS-e2e-workflow-tests/job/master/1634/) if master can run on its own without this PR's change. |
It looks like the tests on the master branch (http://daccs-jenkins.crim.ca/job/PAVICS-e2e-workflow-tests/job/master/1634/) passed so I don't think so. But I don't think that the new errors have anything to do with this PR either since the code here hasn't changed @fmigneault can you explain what changes you made to resolve the error here (#463 (comment)) so that we can help figure out what changed? |
@fmigneault pretty sure 100% not related to that autodeploy change since CRIM Jenkins do not autodeploy anything. That said, for stress-test I also see random errors on our side, on our staging machines where we track |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approve in spirit as I do not use Weaver.
run tests |
E2E Test ResultsDACCS-iac Pipeline ResultsBuild URL : http://daccs-jenkins.crim.ca:80/job/DACCS-iac-birdhouse/2703/Result ✅ SUCCESS BIRDHOUSE_DEPLOY_BRANCH : update-weaver DACCS_IAC_BRANCH : master DACCS_CONFIGS_BRANCH : master PAVICS_E2E_WORKFLOW_TESTS_BRANCH : master PAVICS_SDI_BRANCH : master DESTROY_INFRA_ON_EXIT : true PAVICS_HOST : https://host-140-216.rdext.crim.ca PAVICS-e2e-workflow-tests Pipeline ResultsTests URL : http://daccs-jenkins.crim.ca:80/job/PAVICS-e2e-workflow-tests/job/master/1639/NOTEBOOK TEST RESULTS |
@mishaschwartz @tlvu ⬆️ Retested and everything worked. Seems like the previous errors were sporadic issues... |
Overview
See changes in https://pavics-weaver.readthedocs.io/en/latest/changes.html#changes-5-6-1
Running here: https://hirondelle.crim.ca/weaver/versions
Corresponding changes evaluated during OGC initiatives with cross-platform provider interoperability tests.
Changes
Non-breaking changes
Weaver: bump version to 5.6.1.
Weaver: WPS retry logic on post-compose step.
--network birdhouse_default
to the Dockercurl
image to allow HTTP requests to properly resolveagainst the running services (WPS bird providers, Weave and Magpie). In some cases, this network would not
be automatically resolved.
Breaking changes
Related Issue / Discussion
Merge the PR since it has issues running the CI somehow. Replace by this one all together.
Additional Information
CI Operations
birdhouse_daccs_configs_branch: master
birdhouse_skip_ci: false