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.

Sign up for GitHub

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

Jump to bottom

[5pt] Some integration-tests for aws&smaug are red or can be turned off #302

Open
fridex opened this issue Mar 15, 2022 · 14 comments
Open

[5pt] Some integration-tests for aws&smaug are red or can be turned off #302

fridex opened this issue Mar 15, 2022 · 14 comments
Assignees
@KPostOffice
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@fridex
Copy link
Contributor

fridex commented Mar 15, 2022 •
edited
Loading

Describe the bug

See the most recent report from the AWS&Smaug clusters. We should be able to reproduce the same quality of report for the AWS cluster as for the stage environment.

To Reproduce

See the most recent report for the AWS cluster.

For the test cases we do not want to run in AWS&Smaug clusters, we should set up behave tags.
@fridex
Copy link
Contributor Author

fridex commented Mar 15, 2022 •
edited
Loading

Failing tests

  • Scenario: Browsing logs of container images builds during Amun inspection jobs/Then wait for inspection to finish successfully
  • Dependency Monkey tests
  • Container image analysis
  • Query for metadata for different indices for TensorFlow
  • Querying for the known Python Package Indexes on User API - most probably requires update of the database
    • missing https://pulp.operate-first.cloud/pypi/gym-donkeycar/simple
    • missing https://pulp.operate-first.cloud/pypi/hello-world/simple
    • missing https://pulp.operate-first.cloud/pypi/test/simple
  • schedule solver job
  • advise scenarios failing with HTTP 400
  • provenance scenarios failing with HTTP 400

@fridex
Copy link
Contributor Author

fridex commented Mar 15, 2022

/priority critical-urgent

@sesheta sesheta added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Mar 15, 2022
@Gregory-Pereira
Copy link
Member

/assign

@mayaCostantini
Copy link
Contributor

/assign

@codificat
Copy link
Member

/triage accepted

@sesheta sesheta added the triage/accepted Indicates an issue or PR is ready to be actively worked on. label Mar 15, 2022
@fridex
Copy link
Contributor Author

fridex commented Mar 16, 2022

Based on the discussion we had with @harshad16, we will point integration tests to prod instead of smaug so results will differ. Let's wait for the report sent.

@fridex fridex mentioned this issue Mar 17, 2022
Closed
@fridex
Copy link
Contributor Author

fridex commented Mar 17, 2022

Related action item to be done first: thoth-station/thoth-application#2451

@fridex fridex mentioned this issue Mar 21, 2022
Closed
@goern goern added the kind/feature Categorizes issue or PR as related to a new feature. label Mar 22, 2022
@Gregory-Pereira
Copy link
Member

once the documentation pr gets merged, this will be no longer be blocked by thoth-station/thoth-application#2451.

@harshad16 harshad16 mentioned this issue Apr 11, 2022
Closed
@fridex fridex changed the title Some integration-tests for smaug are red or can be turned off Some integration-tests for aws are red or can be turned off May 2, 2022
@fridex fridex changed the title Some integration-tests for aws are red or can be turned off [5pt] Some integration-tests for aws&smaug are red or can be turned off May 2, 2022
@codificat
Copy link
Member

/sig devsecops

@sesheta sesheta added the sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. label May 9, 2022
@codificat
Copy link
Member

actually this is
/sig stack-guidance
to confirm the status of the various failing scenarios

@sesheta sesheta added the sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. label May 9, 2022
@codificat
Copy link
Member

/remove-sig devsecops

@sesheta sesheta removed the sig/devsecops Categorizes an issue or PR as relevant to SIG DevSecOps. label May 9, 2022
@sesheta
Copy link
Member

sesheta commented Aug 7, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 7, 2022
@harshad16
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 9, 2022
@codificat codificat moved this to 🔖 Ready in Planning Board Aug 22, 2022
@codificat codificat moved this from 🔖 Ready to 🏗 In progress in Planning Board Sep 24, 2022
@mayaCostantini mayaCostantini removed their assignment Dec 2, 2022
@codificat codificat moved this from 🏗 In progress to 📋 Backlog in Planning Board Jan 16, 2023
@codificat codificat moved this from 📋 Backlog to 🔖 Next in Planning Board Jan 23, 2023
@KPostOffice
Copy link
Member

Running tests and looking into failing ones in stage. Running tests takes multiple hours, so this is slow going.

@goern goern added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Feb 7, 2023
@goern goern moved this from 🔖 Next to 📋 Backlog in Planning Board Feb 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KPostOffice KPostOffice

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Planning Board
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
8 participants
@goern @codificat @fridex @harshad16 @KPostOffice @Gregory-Pereira @sesheta @mayaCostantini