Build #3,205

Plan branch:
Acceptance tests using different clients concurrently. Environment deployed from packages.

Build: #3205 failed Child of ODSRV-OZP-2031

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
57 minutes
Labels
None
Revision
a3e3f2732e7723d0fe7b40928e3b07e3817296f6
Total tests
517
Fixed in
#3207 (Child of ODSRV-OZP-2032)

Tests

Responsible

  • Jakub Pilch Jakub Pilch Automatically assigned

Code commits

Author Commit Message Commit date
Jakub Pilch Jakub Pilch a3e3f2732e7723d0fe7b40928e3b07e3817296f6 Pull request #796: VFS-11821 add checking QoS column before and after adding storage parameter
Merge in VFS/onedata-acceptance from feature/VFS-11821-acc-test-check-qos-column-after-state-changed2 to develop

* commit '98c65e089a0eefe17b54050548398617b27bdd6e':
  VFS-11821 add checking QoS column before and after adding storage parameter
Jakub Pilch Jakub Pilch 98c65e089a0eefe17b54050548398617b27bdd6e VFS-11821 add checking QoS column before and after adding storage parameter
Bamboo Agent <bamboo@cloud.plgrid.pl> Bamboo Agent <bamboo@cloud.plgrid.pl> 5f1825dba0ce288d34c50046b414945a79eef693 Update refs to origin/develop.

Tests

New test failures 1
Status Test View job Duration
Collapse Failed test_directories_times test_user_changes_directory_using_client2_and_using_client1_sees_that_modification_time_has_changed[1oz_1op_1oc-oneclient1-web GUI]
Directories times 2 mins 
AssertionError: Time comparison failed.  Time1: modification = 1722628206.0  Time2: modification = 1722628206.0  Comparator: greater
request = <FixtureRequest for <Function 'test_user_changes_directory_using_client2_and_using_client1_sees_that_modification_time_has_changed[1oz_1op_1oc-oneclient1-web GUI]'>>

    @pytest.mark.usefixtures(*function_args)
    def scenario_wrapper(request):
>       _execute_scenario(feature, scenario, request, encoding)

/usr/local/lib/python3.8/dist-packages/pytest_bdd/scenario.py:227: 
(35 more lines...)

Jira issues

IssueDescriptionStatus
Unknown Issue TypeVFS-11821Could not obtain issue details from Jira