Skip to content

Conversation

@shiva-istari
Copy link
Contributor

No description provided.

@github-actions github-actions bot added area/testing Testing related issues go Pull requests that update Go code labels Dec 4, 2025
@blacksmith-sh

This comment has been minimized.

@matthewmcneely matthewmcneely changed the title Unskip previously skipped tests chore(test): unskip previously skipped tests Dec 4, 2025
@blacksmith-sh

This comment has been minimized.

@blacksmith-sh

This comment has been minimized.

@blacksmith-sh

This comment has been minimized.

@github-actions github-actions bot added the area/core internal mechanisms label Dec 8, 2025
@matthewmcneely
Copy link
Contributor

@shiva-istari You missed two added skips in systest/backup/nfs-backup/backup_test.go, lines 41 and 47

@shiva-istari
Copy link
Contributor Author

nfs-backup/backup_test.go

@matthewmcneely What is the context behind skipping them? Are they flaky? I haven’t seen them failing recently.

@matthewmcneely
Copy link
Contributor

nfs-backup/backup_test.go

@matthewmcneely What is the context behind skipping them? Are they flaky? I haven’t seen them failing recently.

@shiva-istari They would fail often when we were on the shared runners between the move.

@blacksmith-sh
Copy link
Contributor

blacksmith-sh bot commented Dec 11, 2025

Found 1 test failure on Blacksmith runners:

Failure

Test View Logs
github.com/dgraph-io/dgraph/v25/systest/backup/nfs-backup/TestBackupHAClust View Logs

Fix in Cursor

@shiva-istari shiva-istari requested a review from a team as a code owner December 12, 2025 05:41
@shiva-istari
Copy link
Contributor Author

nfs-backup/backup_test.go

@matthewmcneely What is the context behind skipping them? Are they flaky? I haven’t seen them failing recently.

@shiva-istari They would fail often when we were on the shared runners between the move.
@matthewmcneely When I unskipped these tests, they started failing because they’re unable to find the mapped port of the container. Surprisingly, they pass every time when run locally. I added retry logic to fetch the container info, but they’re still failing. Should I dig into this further, or leave them skipped for now? This will require more work.

@matthewmcneely
Copy link
Contributor

Should I dig into this further, or leave them skipped for now? This will require more work.

I think it's worth spending a little time on this. Why do all the other tests that rely on getting the mapped port of the container pass? What about your local env (OSX?) is different from the runner?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/core internal mechanisms area/testing Testing related issues go Pull requests that update Go code

Development

Successfully merging this pull request may close these issues.

4 participants