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

gitlab test often fails when unrelated to the PR changes #2185

Closed
gauron99 opened this issue Feb 27, 2024 · 1 comment
Closed

gitlab test often fails when unrelated to the PR changes #2185

gauron99 opened this issue Feb 27, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@gauron99
Copy link
Contributor

gauron99 commented Feb 27, 2024 •
edited
Loading

gitlab test fails in PR actions for integration tests even when unrelated to the PR change at hand.

fails with timeouts

test is skipped here: #2186 for now until its resolved
@gauron99 gauron99 mentioned this issue Feb 27, 2024
Merged
@gauron99 gauron99 changed the title gitlab test often fails when unrelated to the issue gitlab test often fails when unrelated to the PR changes Mar 5, 2024
@gauron99 gauron99 mentioned this issue May 22, 2024
Merged
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Jun 4, 2024

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matejvasek @gauron99