-
Notifications
You must be signed in to change notification settings - Fork 68
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
update @io_bazel_rules_go//go:def.bzl for https://github.com/bazelbui… #143
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, there seems to be an issue with rules_go:
ERROR: error loading package '': Every .bzl file must have a corresponding package, but '@io_bazel_rules_go//go:def.bzl' does not have one. Please create a BUILD file in the same or any parent directory. Note that this BUILD file does not need to do anything except exist.
--
| Traceback (most recent call last):
| File "bazelci.py", line 3655, in <module>
| sys.exit(main())
| File "bazelci.py", line 3635, in main
| bazel_version=task_config.get("bazel") or configs.get("bazel"),
| File "bazelci.py", line 1285, in execute_commands
| bazel_version = print_bazel_version_info(bazel_binary, platform)
| File "bazelci.py", line 1539, in print_bazel_version_info
| + ["--nosystem_rc", "--nohome_rc", "info"]
| File "bazelci.py", line 2281, in execute_command
| args, shell=shell, check=fail_if_nonzero, env=os.environ, cwd=cwd
| File "/usr/lib/python3.6/subprocess.py", line 438, in run
| output=stdout, stderr=stderr)
| subprocess.CalledProcessError: Command '['bazel', '--nosystem_rc', '--nohome_rc', 'info']' returned non-zero exit status 1.
| 🚨 Error: The command exited with status 1
@davidzchen it should be good now. I updated |
Gentle ping. This project remains broken on Bazel CI -- we'll need to disable it on Bazel CI if this isn't resolved soon. |
@davidzchen can we merge this PR as the project is still broken on Bazel CI? |
Merged. Sorry for the delay. Thank you for your contribution! |
Still failing with
|
Hmm, it seems rules_nodejs is new enough. |
Oh, I see, it's because downstream was testing rules_sass at an old commit because our main build was scheduled to run with "master" branch, which caused the "last green commit" not to be updated for rules_sasa. Fixed now! |
…ld/continuous-integration/issues/1404