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

[CI] Kuma adapter tests failing #430

Open
sandramsc opened this issue Feb 22, 2024 · 5 comments · May be fixed by meshery/meshery#12890
Open

[CI] Kuma adapter tests failing #430

sandramsc opened this issue Feb 22, 2024 · 5 comments · May be fixed by meshery/meshery#12890
Labels
area/ci issue/willfix This will be worked on

Comments

@sandramsc
Copy link
Member

Current Behavior

Currently the Kuma adapter tests are failing

Desired Behavior

The tests should be able to pass at all stages, resulting in a successfully implemented workflow.

Implementation

The Meshery Kuma adapter Dockerfile needs an image update, Alpine… with glibc..

Acceptance Tests

Contributor Guides and Resources

@sandramsc sandramsc self-assigned this Feb 22, 2024
Copy link

welcome bot commented Feb 22, 2024

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Contributors' Welcome Guide, engage in the discussion forum, and be sure to join the community Slack.

Copy link

stale bot commented Apr 11, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the issue/stale Issue has not had any activity for an extended period of time label Apr 11, 2024
Copy link

stale bot commented Apr 22, 2024

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.

@stale stale bot closed this as completed Apr 22, 2024
@sandramsc sandramsc reopened this Apr 22, 2024
@stale stale bot removed the issue/stale Issue has not had any activity for an extended period of time label Apr 22, 2024
@sandramsc
Copy link
Member Author

Not resolved

@devhindo
Copy link
Contributor

I recently opened a pr that could solve this issue
I can't confirm as the logs of the action you mentioned is expired

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci issue/willfix This will be worked on
Projects
None yet
3 participants