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

test: update environment spec to work with windows #3358

Merged
merged 2 commits into from
Mar 8, 2022

Conversation

devversion
Copy link
Contributor

@devversion devversion commented Mar 8, 2022

It looks like the environment spec started failing on Windows. It was
thought that this started happening with 4a025c0,
but it turnes out that this failed many commits before but a Buildkite status
just did not show up in the commit history (making it look like the PnP commit
caused the failures).

Root-cause seems to be 7993296 which changed the RUNFILES variable.

It looks like the environment spec started failing on Windows. It was
thought that this started happening with 4a025c0,
but it turnes out that this failed many commits before but a Buildkite status
just did not show up in the commit history (making it look like the PnP commit
caused the failures).
@devversion devversion marked this pull request as ready for review March 8, 2022 16:54
@devversion devversion force-pushed the env-spec-windows-fix branch from c599858 to 4adda37 Compare March 8, 2022 17:01
Looks like 78aefa3 updated the TypeScript docs file in the markdown
directly, but not in the source code, causing CI to fail.
@devversion devversion force-pushed the env-spec-windows-fix branch from 4adda37 to 7d0122a Compare March 8, 2022 17:02
@devversion
Copy link
Contributor Author

I've also fixed the docs content test. Not sure why 78aefa3 changed the link. Seems like an invalid one as well.

@alexeagle alexeagle merged commit 8606c50 into bazel-contrib:stable Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants