You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gomote just uses the underlying buildlet mechanisms, which are shared by the build system, so we should understand this more in case it's causing other problems or will cause problems down the road.
When I submitted https://golang.org/cl/138075 I carefully checked the build dashboard for Darwin failures, and (not seeing any), assumed that the test was ok... sounds like that was a mistake. From your note it looks as though the test simply wasn't running (since it didn't get copied over)?
@thanm, I'm not sure what's happening yet. But yeah, perhaps the test just isn't getting copied over or running.
Or more likely: it's getting written but the filesystem is changing the Unicode normalization form or otherwise re-encoding it, and that's confusing gomote which does not do any such thing.
gomote push gets confused by non-ASCII filenames at least on Darwin:
These were added in https://golang.org/cl/138075
gomote just uses the underlying buildlet mechanisms, which are shared by the build system, so we should understand this more in case it's causing other problems or will cause problems down the road.
/cc @thanm @cherrymui @andybons @dmitshur
The text was updated successfully, but these errors were encountered: