Robert Kielty RobertKielty

CI Signal Meeting - KubeCon 2022 Contributor Summit

@puerco @Claudiu Belu @leonardpahlke @krol @RobKielty @arsh @hsalahi @mkorbi @rajula96reddy

Meeting was attended by a mix of SIG Release CI Signalers, people interested in applying to working on CI Signal and developers

Robert Kielty gave an overview of the CI Signal Tooling, demoing how to detect flakes using test grid.
- Demo notes
  - Although some training is required, it is not that difficult to find flaky tests using Testgrid. CI Jobs that have flaky tests are highlighted in the summary pages such as https://testgrid.k8s.io/sig-release-master-blocking and https://testgrid.k8s.io/sig-release-master-informing; when you drill down into a job that is flaking, at the time of the meeting say seek out a flaky failure by mousing over a red cell that shows when a test has failed and move to neighboring runs where the test passed. If the k/k git commit is the same for both a passing run and a failing run, congratulations, yo

	/* Make the dashboard names easier to read */
	#environments-bar-container,
	#tab-bar {
	text-transform: capitalize;
	}
	/* hightlight currently selected tab */
	.goog-tab-selected {
	font-size: 10pt;
	color:#000 !important;

	==================== Test output for //config/tests/testgrids:go_default_test:
	=== RUN TestConfig
	=== RUN TestConfig/Testgroup_ESPv2-continuous-anthos-cloud-run-e2e-cloud-run-http-bookstore
	=== RUN TestConfig/Testgroup_ESPv2-continuous-build
	=== RUN TestConfig/Testgroup_ESPv2-continuous-cloud-run-e2e-app-engine-http-bookstore
	=== RUN TestConfig/Testgroup_ESPv2-continuous-cloud-run-e2e-cloud-function-http-bookstore
	=== RUN TestConfig/Testgroup_ESPv2-continuous-cloud-run-e2e-cloud-run-grpc-echo
	=== RUN TestConfig/Testgroup_ESPv2-continuous-cloud-run-e2e-cloud-run-http-bookstore
	=== RUN TestConfig/Testgroup_ESPv2-continuous-coverage
	=== RUN TestConfig/Testgroup_ESPv2-continuous-e2e-gcloud-build-image

	sudo kind -v10 build node-image
	Starting to build Kubernetes
	+++ [0714 17:13:20] Verifying Prerequisites....
	+++ [0714 17:13:21] Building Docker image kube-build:build-1f03c03652-5-v1.14.4-2
	^[+++ [0714 17:13:48] Syncing sources to container
	+++ [0714 17:13:50] Output from this container will be rsynced out upon completion. Set KUBE_RUN_COPY_OUTPUT=n to disable.
	+++ [0714 17:13:50] Running build command...
	stat /go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/bazel-bin: no such file or directory
	+++ [0714 17:14:24] Building go targets for linux/amd64:
	cmd/kubeadm

	~ go > src  k8s.io  kubernetes  $  release-1.19  kind build node-image --type bazel
	Starting to build Kubernetes
	Starting local Bazel server and connecting to it...
	Loading:
	Loading: 0 packages loaded
	Analyzing: 4 targets (4 packages loaded, 0 targets configured)
	Analyzing: 4 targets (173 packages loaded, 657 targets configured)
	Analyzing: 4 targets (1379 packages loaded, 11640 targets configured)
	Analyzing: 4 targets (2320 packages loaded, 18126 targets configured)
	INFO: Analyzed 4 targets (2320 packages loaded, 18175 targets configured).

	# Launch /bin/bash interactively on your only running container
	# H.B.D (assumptions)
	# 1. You have one and only one container running
	# 2. /bin/bash is present in your built container
	# TODO Make robust enough to handle multiple containers
	alias dbash='docker exec -it $(docker ps --format "{{.Names}}") /bin/bash'
	alias dps='docker ps'

	Executing a shell on a running Docker container

	First get the container id,

	$ docker ps
	CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
	2301f673e1d5 prom/prometheus:latest "/bin/prometheus -co 15 minutes ago Up 15 minutes 0.0.0.0:9090->9090/tcp dreamy_kirch

	then taking the value of the CONTAINER ID from the above docker ps output you can run an interactive shell as follows

	#!/bin/bash
	# Iterate over dirs in a directory
	# ref http://www.tldp.org/LDP/abs/html/parameter-substitution.html for param subs

	TEST_DIR="/tmp/"

	for dir in $TEST_DIR*/ ; do
	echo "Full path : " ${dir}
	dir=${dir%*/} # remove trailing slash
	echo "Path minus trailing /" ${dir}