Follow-ups left open by the station-series cleanup (#466)
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Facilidade para iniciantes
- 35/100
- Tipo de issue
- Bug
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Domínio
- embedded-iot, testing
Direção de pesquisa
Start by reading docs/mt7612u-tx-retry.md and the station harnesses named in the issue: realtek_station_onair.sh, mt7612u_sta_identity.sh, mt7612u_sta_uplink.sh, and mt7612u_ap_onair.sh; inspect the gate_txs implementation and related harness tests. The issue lists several independent fixes and observations, so confirm which follow-ups remain before changing anything. Done means correcting the actionable harness behaviors and documenting the settling limitation, with tests or hardware runs confirming the results.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Left open by #466 (merged as 1134df9): the station-series review follow-ups, part of the #465 harness sweep, the #461 stale-EXT claim in gate_txs, and the txdemo thread-join guards.
From the review (hardware: realtek_station_onair 5/5 on 8812CU + 8812BU + MT7612U AP; uplink A/B against master)
gate_txsstale-EXT claim can over-attribute. One arm on the review bench read61/60, 1 stale-EXT entries claimed, 11 foreign: the arm then received all 60 of its own entries, so the claimed one was not its own (or a MAC duplicate). Printed, not clipped, butsuccessis inflated by one. Suggested self-correction: track own-pktid entries separately and at arm end, if own == n and stale_ext == 1, move the claimed entry back tolate_prev.- The
stale_settledgate cascades. One UNSETTLED arm disables the claim for every following arm until one settles on its own - a chain of seven consecutive 59/60 arms on the review bench. Correct by the documented rule;docs/mt7612u-tx-retry.mdshould say the claim buys little on a unit whose arms do not settle. - The #461 multi-entry loss is far worse on a second unit. Unicast-to-peer gate arms (b-e) landed 0-11/60 own entries on both passes, ~10 per arm carrying the previous arm's pktid, identical on master. Not this PR; recorded here so #461 has the second data point.
realtek_station_onair.sh:tail_mscan be negative (-6 ms in arm C: the finaltx.statstpreceded the lasttx.reportt). Harmless tolive; clamp at 0 or note it in thesummarizecomment.mt7612u_sta_identity.sh: an overrun BSSID gate setsr_bss=2, but the verdictcasehas only0,3,*, so the operator reads "did not pass" for what the exit code calls INCONCLUSIVE. Add a2)branch.mt7612u_sta_uplink.sh:dut_boundis per harness arm (552 s at FRAMES=60, 1128 s at 200) while the header's 25-minute figure covers both arms; the margin for the slower un-ACKed arm at FRAMES=200 is thin. Size it from the measured figure.mt7612u_ap_onair.sh: on the KILL pathreapdropsKIDSwithoutwaiting the killed children, leaving zombies for the rest of the run.- Firmware readability preflight (#465 class). On a host whose MediaTek firmware is zstd-compressed (
/lib/firmware/mediatek/*.bin.zst),sta_fw_linksucceeds, the probe logscannot open firmware/mt7662_rom_patch.bin, and the uplink harness scoresABORTED the DUT did not confirm retry limit 15:with an empty reason. Checking the two blobs are readable through the link turns a dead rig into a refusal in seconds.
From the PR description
- Find the uplink harness's multi-entry status loss (#461).
- Unify the INT/TERM exit code across the station harnesses: realtek_station_onair, mt7612u_sta_onair and mt7612u_sta_identity exit 3; autoack, uplink and ap_onair still exit 130.
- From #465, not in #466: the generic Realtek DUT take, the reconnect cell and the CCMP soak (separate PR).
Done by the review, no action
- The "last arm that sent" form of the stale-EXT claim is now hardware-run (it coincided with the previous-arm form: no arm had every submit fail). The claim fired correctly on the session's first arm: 60/60 with 1 claimed on #466 against 59/60 UNSETTLED with 1 foreign on master.
- Linguagem predominante
- C
- Estrelas
- 56
- Forks
- 29
- Merge médio
- 3h 43min
- PRs com merge (30d)
- 75
Preparar o ambiente
Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de OpenIPC/devourer
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia
-
Follow-ups left open by the 8822B fast bandwidth toggle fix (#584)Talvez já em andamento @josephnef assumiu hoje. Abertaenhancement
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 42/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 12/100
OpenIPC/devourer#579 · 1 comentário ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 12/100
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 8/100
Mantenedores costumam responder em até 1 dia
Todas as issues de OpenIPC/devourer
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
Mantenedores costumam responder em até 1 dia
-
Needs-Triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 66/100
Mantenedores costumam responder em até 2 dias
-
issue: bug report
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 2 dias
-
cross-platform fix-now
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
Mantenedores costumam responder em até 1 dia
-
feature:index kind:crash status:confirmed triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
clice-io/clice#1123 · 1 comentário ·
Mantenedores costumam responder em até 1 dia