Test report for PR(s) easybuilders/easybuild-easyconfigs#26977
Build succeeded for 3 out of 3 (total: 2 mins 33 secs) (3 easyconfigs in total)
-
SUCCESS optree-0.20.0-GCCcore-15.2.0.eb
-
SUCCESS tlparse-0.4.8-GCCcore-15.2.0.eb
| /* =============================================================================== CONSULTAS DE SQL: OR, NOT, NULL, | |
| LIMIT, INSERT, UPDATE & DELETE | |
| Base de datos: Northwind (SQLite) Nayeli Muñoz BDA 9AM | |
| =============================================================================== */ | |
| /* =============================================================================== | |
| 1. CONSULTA DE SQL: OR | |
| Base de datos: Northwind (SQLite) | |
| =============================================================================== */ |
| Pipeline still running ... | |
| PipelineRun is still running: Tasks Completed: 23 (Failed: 0, Cancelled 0), Incomplete: 1, Skipped: 7 | |
| [set-github-status-pending : set-github-status] unable to retrieve container logs for cri-o://2fa6dade1741b34ddcd2e599953ca80d14c535936f951a481e81afda3465cf8d | |
| [set-github-started-label : post-comment] unable to retrieve container logs for cri-o://b862b9ed6710a228bda30e35c996d8c3decc82f842905791afa1a71af4dc69ba | |
| [set-env : set-env] unable to retrieve container logs for cri-o://22a7e0aa877e42958fa685589b6ecaccbb269c19353dda97717cd6d8ee8d2a8c | |
| [clone-repository : clone] unable to retrieve container logs for cri-o://75336dae7c4aff35a90edf2258d0829fd619e8392c8c583d3690fc8f17ec9525 |
| <!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>AGENTS.md paired comparison</title><style> | |
| :root{--ink:#192b3b;--muted:#5b6c7a;--border:#dce4e9;--left:#fff0d8;--right:#e1efff}*{box-sizing:border-box}body{margin:0;background:#f4f7fa;color:var(--ink);font:15px/1.5 system-ui,-apple-system,sans-serif}main{max-width:1680px;margin:auto;padding:32px}header{max-width:1100px;margin-bottom:24px}.title{font-size:32px;font-weight:750;letter-spacing:-.6px;margin:0 0 12px}.subtitle{font-size:17px;color:var(--muted)}a{color:#185f99}nav{display:flex;gap:8px;flex-wrap:wrap;margin:18px 0}nav a{background:white;border:1px solid var(--border);border-radius:6px;padding:7px 12px;text-decoration:none}.toolbar{display:flex;gap:18px;align-items:center;flex-wrap:wrap;background:white;border:1px solid var(--border);border-radius:8px;padding:12px 16px;margin-bottom:22px}select,button{font:inherit;padding:6px 10px;border:1px solid #b5c5d1;border-radius:5 |
Test report for PR(s) easybuilders/easybuild-easyconfigs#26977
Build succeeded for 3 out of 3 (total: 2 mins 33 secs) (3 easyconfigs in total)
SUCCESS optree-0.20.0-GCCcore-15.2.0.eb
SUCCESS tlparse-0.4.8-GCCcore-15.2.0.eb
| Pipeline still running ... | |
| PipelineRun is still running: Tasks Completed: 34 (Failed: 1, Cancelled 0), Incomplete: 1, Skipped: 19 | |
| [get-pr-number : parse-pr-url] 2026-09-27T00:12:04.98Z + echo -n 11290 | |
| [get-pr-number : parse-pr-url] 2026-09-27T00:12:04.98Z + tee /tekton/results/git_pr_number | |
| [get-pr-number : parse-pr-url] 2026-09-27T00:12:04.98Z 11290 | |
| [acquire-lease : create-lease] 2026-09-27T00:12:13.07Z + calculate_duration_in_seconds 90m | |
| [acquire-lease : create-lease] 2026-09-27T00:12:13.07Z + '[' m == m ']' | |
| [acquire-lease : create-lease] 2026-09-27T00:12:13.07Z + TOTAL_DURATION_IN_SECONDS=5400 | |
| [acquire-lease : create-lease] 2026-09-27T00:12:13.07Z + export TOTAL_DURATION_IN_SECONDS |
A pattern for building personal knowledge bases using LLMs.
This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.
Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.
A poker round progresses through a strict sequence of states. The game engine uses these states to know what is allowed at any moment.
This document explains every concept from the ground up — what each term means, why it exists, how it works, and how everything connects together. By the end, you will have a complete understanding of how a poker round is structured and why every rule exists.
tests/e2e/hardening_e2e_runner.js is a script you run from the command
line (node tests/e2e/hardening_e2e_runner.js) that checks the backend
server directly — no browser involved. It's a command-line copy of the
browser-based "Hardening Scenarios" feature inside the PokerFrontend app
(see frontend_runners_hardening.md), built
so the same checks can run without needing a browser open.
For the full list of scenarios and a deep, per-check technical breakdown,
File: tests/e2e/th.three_handed.js
Run: node tests/e2e/th.three_handed.js (requires a live server + Postgres)
Subsystem under test: runExtended() in variant.realistic.extended.js — Texas Hold'em, 3-Handed archetype (TAG + LAG + NIT, 6 rounds, SB/BB 5/10, default 1000 starting chips).
File: tests/e2e/th.tag_vs_fish.js
Run: node tests/e2e/th.tag_vs_fish.js (requires a live server + Postgres)
Subsystem under test: runExtended() in variant.realistic.extended.js — Texas Hold'em, 2 TAGs vs 2 FISHes archetype (interleaved TAG/FISH/TAG/FISH, 8 rounds, SB/BB 5/10, default 1000 starting chips).