Scott Beddall semick-dev

Failure details

[Build Log](- Build Log
The test

removingHandlerCancelsTimeout
org.opentest4j.AssertionFailedError: expected: <null> but was: <ScheduledFutureTask@5454300b(success, task: COMPLETED, deadline: 2707436309, period: 0)>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)

Summary

The audit log is built by the proxy continuously adding atomic entries to a ConcurrentQueue, to avoid any chance of multithread locking causing a log to be lost or written at the wrong time. Relevant tools PR

2024-08-04T08:23:25.1419890Z 84f69d4d-5987-4a75-a2a2-d1c1f41908fd,2024-08-04T08:09:32.4381237Z,,,Starting playback for path sdk/storage/azure-storage-file-share/src/test/resources/session-records/FileServiceApiTests.setAndGetPropertiesWithInvalidArgs[1].json, which will return recordingId 84f

Vim notes

Installation via marketplace

Start with VsCodeVim marketplace extension.

Normal Mode

To return to normal mode:

How to debug test-proxy issues

This writeup is NOT a reference on how to install or run the test-proxy, it is a shortcut guide to helping a test-proxy dev debug each language's tests.

.NET

To run storage tests, `azurite` must be installed

Install npm, ensure node is available on PATH
Install npm version of azurite, npm install -g azurite

Getting a `pypy` Virtual Env on WSL

All of the details in this instruction are being run from the default user folder of your WSL. For me, that's /home/semick/. ~ is also used to refer to this same /home/semick directory.

So install Ubuntu 20.04 LTS from Microsoft Store! (If you aren't using the new windows terminal I HIGHLY recommend it)

Finally, get a usable `venv` for pypy39

sudo apt update &amp;&amp; sudo apt upgrade

`azure-resourcemanager-compute` on ubuntu 20.04

Get `mvn`

wget https://dlcdn.apache.org/maven/maven-3/3.8.8/binaries/apache-maven-3.8.8-bin.tar.gz
sudo tar -xzf apache-maven-3.8.8-bin.tar.gz -C /opt/
mv /opt/apache-maven-3.8.8 /opt/maven
export MAVEN_HOME=/opt/maven
export PATH=$MAVEN_HOME/bin:$PATH

How to add a devops feed to local configuration for an npm package

Within your package folder (folder containing package.json for your package), locate where the .npmrc for the package is located. Usually it's right alongside the package.json. Creating an .npmrc with the feed is covered in a step below.
- For openapi-alps this is located under common/config/rush/.npmrc
Ensure your project .npmrc has a reference to the feed containing your packages.
- To get detailed instructions from devops, go to the feed and click Connect to Feed (top right button), then click NPM, and change from Windows tab to Other. The Other tab is excellent to use for linux/mac connections.

Update your project .npmrc with the following

# "registry" is a url, don't make it multiline!

	Set-StrictMode -Version 4
	$AVAILABLE_TEST_PROXY_BINARIES = @{
	"Windows" = @{
	"AMD64" = @{
	"system" = "Windows"
	"machine" = "AMD64"
	"file_name" = "test-proxy-standalone-win-x64.zip"
	"executable" = "Azure.Sdk.Tools.TestProxy.exe"
	}
	}

	FROM debian:bullseye-slim

	ENV LANG C.UTF-8
	ENV BOOTSTRAP_HASKELL_NONINTERACTIVE 1

	# [Option] Install zsh
	ARG INSTALL_ZSH="true"
	# [Option] Upgrade OS packages to their latest versions
	ARG UPGRADE_PACKAGES="false"

	import argparse

	from ci_tools.functions import discover_targeted_packages
	from ci_tools.parsing import ParsedSetup, update_build_config
	from ci_tools.functions import omit_mgmt

	if __name__ == "__main__":
	parser = argparse.ArgumentParser(description="")

	parser.add_argument(