Skip to content
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

Test SOSAPI PUTs with a bucket having a dot in its name #2153

Open
wants to merge 2 commits into
base: development/2.6
Choose a base branch
from

Conversation

williamlardier
Copy link
Contributor

This allows to test that the custom route is accepting such buckets.

For now we have failures - to be merged once we bump ZKOP to the latest version

Failures:

1) Scenario: PUT routes for SOSAPI configuration files # features/sosapi.feature:32
   ✔ Before # hooks/Logger.ts:36
   ✔ Before # hooks/versionTags.ts:6
   ✔ Before # common/hooks.ts:20
   ✔ Given a "Non versioned" bucket with dot # common/common.ts:104
   ✔ When I PUT the "invalid" "capacity.xml" XML file # steps/sosapi.ts:49
   ✖ Then the request should be "not accepted" # steps/sosapi.ts:69
       AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

       true !== false

           + expected - actual

           -true
           +false

           at Zenko.<anonymous> (/ctst/steps/sosapi.ts:72:12)
   ✔ After # hooks/Logger.ts:60

2) Scenario: PUT routes for SOSAPI configuration files # features/sosapi.feature:34
   ✔ Before # hooks/Logger.ts:36
   ✔ Before # hooks/versionTags.ts:6
   ✔ Before # common/hooks.ts:20
   ✔ Given a "Non versioned" bucket with dot # common/common.ts:104
   ✔ When I PUT the "invalid" "system.xml" XML file # steps/sosapi.ts:49
   ✖ Then the request should be "not accepted" # steps/sosapi.ts:69
       AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

       true !== false

           + expected - actual

           -true
           +false

           at Zenko.<anonymous> (/ctst/steps/sosapi.ts:72:12)
   ✔ After # hooks/Logger.ts:60

Issue: ZENKO-4889

This allows to test that the custom route is accepting such
buckets.

Issue: ZENKO-4889
@bert-e
Copy link
Contributor

bert-e commented Sep 24, 2024

Hello williamlardier,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Sep 24, 2024

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@williamlardier
Copy link
Contributor Author

Must be merged after ZENKO-4899 (with latest ZKOP).

@francoisferrand
Copy link
Contributor

/after_pull_request=2142

@bert-e
Copy link
Contributor

bert-e commented Sep 24, 2024

Waiting for other pull request(s)

The current pull request is locked by the after_pull_request option.

In order for me to merge this pull request, run the following actions first:

➡️ Merge the OPEN pull request:

Alternatively, delete all the after_pull_request comments from this pull request.

The following options are set: after_pull_request

@francoisferrand
Copy link
Contributor

/after_pull_request=2028

@bert-e
Copy link
Contributor

bert-e commented Sep 24, 2024

Waiting for other pull request(s)

The current pull request is locked by the after_pull_request option.

In order for me to merge this pull request, run the following actions first:

➡️ Merge the OPEN pull requests:

Alternatively, delete all the after_pull_request comments from this pull request.

The following options are set: after_pull_request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants