agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/karpenter-provider-azure/.github/skills/run-e2e-tests/SKILL.md

run-e2e-tests

Skill559 starsChanged 36 days agoApache-2.0View on GitHub

Run end-to-end (E2E) tests - provider test suites or upstream Karpenter tests, with focus filtering, background execution, and monitoring

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. wealthfolio/wealthfolio★ 9.4ksame name
    2. afadil/wealthfolio★ 9.4ksame name
    3. go-vikunja/vikunja★ 6ksame name
    4. microsoft/vscode-python-environments★ 147same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use FOCUS to filter further (or FDescribe/FIt in code).

    line 13
  2. Very specific:

    Run with nohup so tests continue even if you run other commands or the terminal disconnects:

    line 17
  3. Very specific:

    Run via .github/workflows/e2e.yaml using gh workflow run.

    line 37

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

E2E Tests

Running Tests

  • Provider tests: TEST_SUITE=<suite> make az-e2etests (suites in test/suites/)
  • Upstream tests: FOCUS=<focus> make az-upstream-e2etests (source in Go module cache or upstream repo)

Use FOCUS to filter further (or FDescribe/FIt in code).

Background Execution

Run with nohup so tests continue even if you run other commands or the terminal disconnects:

TEST_SUITE=Consolidation nohup make az-e2etests > /workspaces/karpenter/logs/e2e.log 2>&1 &

Codespace Considerations

Idle suspension kills all processes (default 30min, can be increased under https://github.com/settings/codespaces; only affects new codespaces). Logs in /workspaces (not /tmp) survive for checking after resume.

Monitoring

  • Logs: tail -f <logfile> (or tail -n for spot check)
  • Cluster: kubectl get nodeclaims,nodes,pods -w
  • Events: make az-kevents
  • Azure resources: make az-res
  • Metrics: port-forward to Karpenter pod, /metrics endpoint

GitHub Actions

Run via .github/workflows/e2e.yaml using gh workflow run.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free