CI: no hosted job builds or runs the HTTP extension on macOS

Abierto
#2,388 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
c, github-actions, macos
Área
ci-cd, testing-qa

Línea de trabajo

Start with ci.yml and nightly.yml to see how the existing Linux server job builds and runs HTTP sections; compare its required check entry in required-checks.txt and tier validation in tools/ci_tier_check.sh. Add a macos-latest job that builds with make http and runs sections 44 and 45, reporting each section and the loaded curl version. Done when the required-check policy is satisfied and docs/BUILTINS.md names the job.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:ci area:http kind:gate-defect

Found on 2026-11-17 while reading the first hosted run of the outbound client (#2375).

What happens

No workflow builds the server profile on macOS. The macOS jobs (macos suite / macos-latest in ci.yml, nightly / macos-15-intel full suite in nightly.yml) build the plain profile, where every HTTP section of the suite skips. From the macOS job of run 44031141523 (a branch of phase2-numbers):

[45h] Request header fields and head boundary (#2373)
SECTION_TIME: [45h] 0.00
[45i] Outbound HTTP exchange and tape (#2375)
SECTION_TIME: [45i] 0.00
  RESULTS: 4932/4932 passed, 0 failed, 26 skipped

grep -n -i "make http\|make server\|build.sh server" over nightly.yml and the release workflows finds nothing, and ci.yml builds the server profile on Linux only.

Why it matters

  • The HTTP server and the outbound client are C that reads bytes from a peer. On macOS that C is compiled by no job, so a build break or a behaviour that differs there is found by a user.
  • The outbound client loads the curl library by name, and its documentation gives the names it looks for on macOS (libcurl.4.dylib, libcurl.dylib). No job loads them. The same release question that #2375 met on Linux (a newer release of the library refusing what an older one returns) is open on macOS and unobserved.
  • #2375's bar asked for its rows "on the macOS lanes of CI". No lane can show them, and the row is being amended to say so and to point here.

Done when

  • A job on macos-latest builds the server profile (make http) and runs the HTTP sections of the suite on that build: 44 and every 45 section that the Linux server job runs.
  • Each of those sections prints its own count line in that job's log, and the job fails when a section that the Linux server job runs is skipped there. A section that cannot run on macOS is named in the job with its reason.
  • The job has its place in required-checks.txt (#1264): whether it runs on a pull request, in the merge queue or nightly is stated there, and tools/ci_tier_check.sh passes.
  • The release of the curl library that the job loaded is printed in its log.
  • docs/BUILTINS.md names that job where it gives the macOS names of the library.

— Claude DevBox

Lenguaje dominante
C
Estrellas
3
Forks
7
Merge medio
3 h 28 min
PR fusionados (30 d)
270

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de InauguralSystems/EigenScript

Todos los issues de InauguralSystems/EigenScript

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.