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

Bazel Remote Cache: TLS tests, basic auth tests failing #1150

Closed
comius opened this issue May 11, 2021 · 7 comments
Closed

Bazel Remote Cache: TLS tests, basic auth tests failing #1150

comius opened this issue May 11, 2021 · 7 comments

Comments

@comius
Copy link
Collaborator

comius commented May 11, 2021

  • TLS tests started failing on 2021-05-07
  • basic auth tests started failing on 2021-05-05, because of a missing test file, since 2021-05-07 same as TLS tests
  • autosheriff blames infra

Link: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/2025#ee9eaee2-0f65-4a58-abb2-cb05bba3b690

Example failure:

WARNING: Writing to Remote Cache:
Error while uploading artifact with digest '5e9f615a82e4dca1e09d9386b774d6c886de22b1395390e3b6988daf91d117bd/144'
Target //:bazel-remote up-to-date:
  bazel-out/k8-fastbuild-ST-3891b650e255/bin/bazel-remote_/bazel-remote
INFO: Elapsed time: 4.230s, Critical Path: 2.74s
INFO: 456 processes: 436 remote cache hit, 19 internal, 1 linux-sandbox.
INFO: Build completed successfully, 456 total actions
INFO: Build completed successfully, 456 total actions
 
grep -A 1 "WARNING: Writing to Remote Cache:" "$tmpdir/unauthenticated_write.log" | \
	tr '\n' '|' > "$tmpdir/unauthenticated_write.log.singleline"
if ! grep --silent "WARNING: Writing to Remote Cache:|BulkTransferException|" "$tmpdir/unauthenticated_write.log.singleline"
then
	# We seem to always have one cache miss with a rebuild.
	# So we expect a single cache write attempt, and it should fail.
	echo "Error: expected a warning when writing to the remote cache fails"
	exit 1
fi
Error: expected a warning when writing to the remote cache fails
Traceback (most recent call last):
  File "bazelci.py", line 3402, in <module>
    sys.exit(main())
  File "bazelci.py", line 3368, in main
    execute_commands(
  File "bazelci.py", line 1089, in execute_commands
    execute_shell_commands(task_config.get("shell_commands", None))
  File "bazelci.py", line 1485, in execute_shell_commands
    execute_command([shell_command], shell=True)
  File "bazelci.py", line 2079, in execute_command
    return subprocess.run(
  File "/usr/lib/python3.8/subprocess.py", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['set -e\necho +++ Run basic auth tests\n.bazelci/basic-auth-tests.sh']' returned non-zero exit status 1.
@philwo
Copy link
Member

philwo commented May 11, 2021

That's pretty mysterious. I think their test might be failing due to the error message having changed (probably just no longer prints the weird "BulkTransferException" thing, but a more user-friendly "Error while uploading artifact with digest [...]" message?), but Culprit Finder should have correctly found the commit that changed the error message then.

@coeuvre @meteorcloudy Any idea?

@coeuvre
Copy link
Member

coeuvre commented May 12, 2021

Yes, the message for upload errors is changed by bazelbuild/bazel@913a985 which is included by 4.1.0rc1.

@meteorcloudy
Copy link
Member

meteorcloudy commented May 12, 2021

I think autosheriff is correct this time, it's caused by the change of presubmit.yml of Bazel Remote Cache the project:
buchgr/bazel-remote@f7f9c9d

Looks like this change works with Bazel 4.0 but not with 4.1 or HEAD due to bazelbuild/bazel@913a985

/cc @mostynb

@mostynb
Copy link
Contributor

mostynb commented May 12, 2021

Thanks for the heads-up. I will take a look.

mostynb added a commit to mostynb/bazel-remote that referenced this issue May 12, 2021
The bazel error message for upload failures has changed in bazel 4.1.0rc1,
which broke part of our auth tests. We shouldn't rely on specific logs for
tests- let's disable this part of the test while we look for a more robust
solution.

bazelbuild/continuous-integration#1150
@mostynb
Copy link
Contributor

mostynb commented May 12, 2021

I have disabled this fragile test in bazel-remote.

@meteorcloudy
Copy link
Member

Thank you!

@comius
Copy link
Collaborator Author

comius commented May 14, 2021

Thanks!

@comius comius closed this as completed May 14, 2021
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

No branches or pull requests

5 participants