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

fix: remove simple build dependency from build and integration tests #1309

Merged
merged 3 commits into from
Aug 7, 2024

Conversation

tisutisu
Copy link
Contributor

@tisutisu tisutisu commented Aug 5, 2024

Description

This PR includes changes to remove dependency on simple build usage from build and integration service related suites

Issue ticket number and link

https://issues.redhat.com/browse/STONEBLD-2611

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Locally and build-definitions CI with this PR

Checklist:

  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
  • I have updated labels (if needed)

Expect(err).ShouldNot(HaveOccurred())

for _, testScenario := range *integrationTestScenarios {
Expect(f.AsKubeAdmin.IntegrationController.DeleteIntegrationTestScenario(&testScenario, testNamespace)).To(Succeed())

Check failure

Code scanning / gosec

Implicit memory aliasing in for loop. Error test

Implicit memory aliasing in for loop.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be addressed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it was there in the code already, haven't changed it, I just copied here.

@tisutisu
Copy link
Contributor Author

tisutisu commented Aug 5, 2024

/test redhat-appstudio-e2e

@konflux-ci-qe-bot
Copy link

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-2vfrw-spts9 /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-2vfrw-spts9

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@flacatus
Copy link
Collaborator

flacatus commented Aug 5, 2024

Screenshot from 2024-08-05 17-23-38

@konflux-ci-qe-bot
Copy link

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-jgk7b-sk6fb /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-jgk7b-sk6fb

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@konflux-ci-qe-bot
Copy link

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-dvvwt-j6mr7 /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-dvvwt-j6mr7

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@tisutisu
Copy link
Contributor Author

tisutisu commented Aug 6, 2024

/test redhat-appstudio-e2e

@konflux-ci-qe-bot
Copy link

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-x2s5z-gm6lz /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-x2s5z-gm6lz

For instructions on how to install ORAS, please refer to the ORAS installation guide.

Copy link

openshift-ci bot commented Aug 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jinqi7

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved label Aug 6, 2024
@flacatus
Copy link
Collaborator

flacatus commented Aug 6, 2024

/lgtm

@psturc
Copy link
Member

psturc commented Aug 6, 2024

/hold

tests/build/const.go Show resolved Hide resolved
Copy link
Member

@psturc psturc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple of questions/suggestions, otherwise lgtm

tests/konflux-demo/config/scenarios.go Show resolved Hide resolved
Expect(err).ShouldNot(HaveOccurred())

for _, testScenario := range *integrationTestScenarios {
Expect(f.AsKubeAdmin.IntegrationController.DeleteIntegrationTestScenario(&testScenario, testNamespace)).To(Succeed())
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be addressed?

tests/konflux-demo/konflux-demo.go Show resolved Hide resolved
@tisutisu
Copy link
Contributor Author

tisutisu commented Aug 6, 2024

Probably a conflict during execution
"build.appstudio.openshift.io/status": "{\"pac\":{\"state\":\"error\",\"error-id\":53,\"error-message\":\"53: Git repository is already handled by Pipelines as Code\"},\"message\":\"done\"}",

/retest

@konflux-ci-qe-bot
Copy link

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-wcvx7-xwjv2 /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-wcvx7-xwjv2

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@konflux-ci-qe-bot
Copy link

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-cmrp4-df762 /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-cmrp4-df762

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@psturc
Copy link
Member

psturc commented Aug 6, 2024

Probably a conflict during execution "build.appstudio.openshift.io/status": "{\"pac\":{\"state\":\"error\",\"error-id\":53,\"error-message\":\"53: Git repository is already handled by Pipelines as Code\"},\"message\":\"done\"}",

/retest

/retest

these failures make me think whether we should rather start creating unique repositories for PaC tests in ephemeral clusters instead of reusing a single repositoriy for multiple tests, which could lead to such conflicts 🤔

@tisutisu
Copy link
Contributor Author

tisutisu commented Aug 6, 2024

Probably a conflict during execution "build.appstudio.openshift.io/status": "{\"pac\":{\"state\":\"error\",\"error-id\":53,\"error-message\":\"53: Git repository is already handled by Pipelines as Code\"},\"message\":\"done\"}",
/retest

/retest

these failures make me think whether we should rather start creating unique repositories for PaC tests in ephemeral clusters instead of reusing a single repositoriy for multiple tests, which could lead to such conflicts 🤔

suspecting it is due to the parallel running e2e-tests in konflux CI (that we are trying to onboard) and e2e-tests running in openshift-ci.

Copy link

openshift-ci bot commented Aug 6, 2024

@tisutisu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/redhat-appstudio-e2e ba9b7f1 link false /test redhat-appstudio-e2e

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@konflux-ci-qe-bot
Copy link

@psturc: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-7z84z-dss5m /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-7z84z-dss5m

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@psturc
Copy link
Member

psturc commented Aug 6, 2024

Probably a conflict during execution "build.appstudio.openshift.io/status": "{\"pac\":{\"state\":\"error\",\"error-id\":53,\"error-message\":\"53: Git repository is already handled by Pipelines as Code\"},\"message\":\"done\"}",
/retest

/retest
these failures make me think whether we should rather start creating unique repositories for PaC tests in ephemeral clusters instead of reusing a single repositoriy for multiple tests, which could lead to such conflicts 🤔

suspecting it is due to the parallel running e2e-tests in konflux CI (that we are trying to onboard) and e2e-tests running in openshift-ci.

I think this could be happening even after we disable openshift-ci, i.e. in cases, when multiple jobs (across repositories) are running at the same time. IMO creation of unique test repository for each test could eliminate this problem.

@psturc
Copy link
Member

psturc commented Aug 7, 2024

/test (this should trigger retest just in konflux-ci)

Copy link

openshift-ci bot commented Aug 7, 2024

@psturc: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

  • /test images
  • /test load-test-ci-100u
  • /test load-test-ci-10u
  • /test load-test-ci-1u
  • /test load-test-ci-50u
  • /test max-concurrency-advanced
  • /test max-concurrency-basic

The following commands are available to trigger optional jobs:

  • /test redhat-appstudio-e2e

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-konflux-ci-e2e-tests-main-images

In response to this:

/test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@konflux-ci-qe-bot
Copy link

@psturc: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-tpfkr-jczxv /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-tpfkr-jczxv

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@konflux-ci-qe-bot
Copy link

@tisutisu: The following test finished, in case test failed say /retest to rerun all failed tests:

PipelineRun name Command
konflux-e2e-pcn6d-dlgsx /retest

To inspect your test artifacts make sure you have installed ORAS in your local machine. To inspect all test artifacts execute:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-qe-incubator/konflux-qe-oci-storage:konflux-e2e-pcn6d-dlgsx

For instructions on how to install ORAS, please refer to the ORAS installation guide.

@tisutisu
Copy link
Contributor Author

tisutisu commented Aug 7, 2024

Probably a conflict during execution "build.appstudio.openshift.io/status": "{\"pac\":{\"state\":\"error\",\"error-id\":53,\"error-message\":\"53: Git repository is already handled by Pipelines as Code\"},\"message\":\"done\"}",
/retest

/retest
these failures make me think whether we should rather start creating unique repositories for PaC tests in ephemeral clusters instead of reusing a single repositoriy for multiple tests, which could lead to such conflicts 🤔

suspecting it is due to the parallel running e2e-tests in konflux CI (that we are trying to onboard) and e2e-tests running in openshift-ci.

I think this could be happening even after we disable openshift-ci, i.e. in cases, when multiple jobs (across repositories) are running at the same time. IMO creation of unique test repository for each test could eliminate this problem.

@psturc current conflict was in the test changes itself, fixed with this commit, I think conflict during parallel running needs to be addressed across all the suites, so created a story to address that, it would be good keep that enhancement in a separate story. Please take a look again, replied in the comments.

@psturc
Copy link
Member

psturc commented Aug 7, 2024

/unhold
/lgtm

@openshift-ci openshift-ci bot added the lgtm label Aug 7, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit d70d686 into konflux-ci:main Aug 7, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants