-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
os: TestRootConsistencyLstat/dotdot_in_path_after_symlink failures [consistent failure] #70491
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Comments
gopherbot
added
the
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
label
Nov 21, 2024
Found new dashboard test flakes for:
2024-11-21 02:17 gotip-netbsd-arm64 go@f9698788 os.TestRootConsistencyLstat/dotdot_in_path_after_symlink (log)
2024-11-21 02:18 gotip-netbsd-arm64 go@a9428eab os.TestRootConsistencyLstat/dotdot_in_path_after_symlink (log)
2024-11-21 05:01 gotip-netbsd-arm64 go@b631b8e6 os.TestRootConsistencyLstat/dotdot_in_path_after_symlink (log)
2024-11-21 05:01 gotip-netbsd-arm64 go@a2a4f007 os.TestRootConsistencyLstat/dotdot_in_path_after_symlink (log)
|
Found new dashboard test flakes for:
2024-11-21 10:40 gotip-netbsd-arm64 go@28f4e14e os.TestRootConsistencyLstat/dotdot_in_path_after_symlink (log)
|
Found new dashboard test flakes for:
2024-11-20 23:27 gotip-netbsd-arm64 go@adc9c455 os.TestRootConsistencyLstat/dotdot_in_path_after_symlink (log)
|
Found new dashboard test flakes for:
2024-11-20 23:21 gotip-netbsd-arm64 go@c315862c os.TestRootConsistencyLstat/dotdot_in_path_after_symlink (log)
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: