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

Investigate state of agw-docker-load-test.yml #14228

Closed
LKreutzer opened this issue Oct 20, 2022 · 3 comments · Fixed by #14824
Closed

Investigate state of agw-docker-load-test.yml #14228

LKreutzer opened this issue Oct 20, 2022 · 3 comments · Fixed by #14824
Assignees
Labels
component: ci All updates on CI (Jenkins/CircleCi/Github Action)

Comments

@LKreutzer
Copy link
Contributor

Ivestigate state of agw-docker-load-test.yml

If possible remove and clean up.

@LKreutzer LKreutzer added the component: ci All updates on CI (Jenkins/CircleCi/Github Action) label Oct 20, 2022
@Neudrino
Copy link
Contributor

@LKreutzer
Copy link
Contributor Author

Possible duplicates:

* [Investigate state of `agw-docker-load-test.yml` #14228](https://github.com/magma/magma/issues/14228)

* [Create CI job for running the load tests #14318](https://github.com/magma/magma/issues/14318)

Keeping this open - it seems they are unrelated because the load tests are not executed anywhere - in fact the Make targets have been removed and this workflow is unchanged. The bazel script is not run in CI.

@mpfirrmann
Copy link
Contributor

The last run was failing with an authentication failure at AWS. The workflow uses secrets.FB_AWS_ACCESS_KEY and secrets.FB_AWS_SECRET_ACCESS_KEY. Are they still present / is the AGW account still open?
@maxhbr, do you know anything here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: ci All updates on CI (Jenkins/CircleCi/Github Action)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants