<feed xmlns='http://www.w3.org/2005/Atom'>
<title>accel-ppp.git/.github/workflows/run-tests-bigendian.yml, branch sstp-alloc-invariant</title>
<subtitle>High performance PPTP/L2TP/SSTP/PPPoE/IPoE server for Linux (mirror of https://github.com/accel-ppp/accel-ppp.git)
</subtitle>
<id>https://git.amelek.net/accel-ppp/accel-ppp.git/atom?h=sstp-alloc-invariant</id>
<link rel='self' href='https://git.amelek.net/accel-ppp/accel-ppp.git/atom?h=sstp-alloc-invariant'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/accel-ppp/accel-ppp.git/'/>
<updated>2026-06-10T12:57:46+00:00</updated>
<entry>
<title>ci: harden s390x qemu test against modloop/disk flakes</title>
<updated>2026-06-10T12:57:46+00:00</updated>
<author>
<name>Denys Fedoryshchenko</name>
<email>denys.f@collabora.com</email>
</author>
<published>2026-06-10T12:57:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/accel-ppp/accel-ppp.git/commit/?id=0484b5d7c6c11f6ae832bf504d528e04d5fa31aa'/>
<id>urn:sha1:0484b5d7c6c11f6ae832bf504d528e04d5fa31aa</id>
<content type='text'>
The s390x netboot initramfs ships virtio_net but not virtio_blk; the
block driver only becomes available after the modloop image is
downloaded over the network at boot. When that download fails, sshd
still comes up but /dev/vda never appears and setup-disk dies with
"/dev/vda is not a block device suitable for partitioning".

- Wait for /sys/block/vda/device before running setup-alpine,
  restarting the modloop and hwdrivers services on each retry.
- Log the QEMU console (screen -L) for both VM launches and dump the
  logs at the end of the job, so failures of the second boot (the
  other recurring flake, where ssh never comes back after reboot)
  are debuggable.

Co-Authored-By: Claude Fable 5 &lt;noreply@anthropic.com&gt;
</content>
</entry>
<entry>
<title>ci: Tightening warning condition in dmesg checks</title>
<updated>2026-05-03T23:58:15+00:00</updated>
<author>
<name>Denys Fedoryshchenko</name>
<email>denys.f@collabora.com</email>
</author>
<published>2026-05-03T23:57:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/accel-ppp/accel-ppp.git/commit/?id=a8556b814669802996d30aa06deac4b19327b694'/>
<id>urn:sha1:a8556b814669802996d30aa06deac4b19327b694</id>
<content type='text'>
The boot-time RETBleed: WARNING: Spectre v2 mitigation...
line matches the broad WARNING: regex.
The intent of that pattern was to catch kernel WARN_ON() splats,
which always begin with WARNING: CPU:. We can tighten checks, to avoid false positive.

Signed-off-by: Denys Fedoryshchenko &lt;denys.f@collabora.com&gt;
</content>
</entry>
<entry>
<title>ci: fail workflows on kernel issues found in dmesg</title>
<updated>2026-05-02T12:07:57+00:00</updated>
<author>
<name>Denys Fedoryshchenko</name>
<email>denys.f@collabora.com</email>
</author>
<published>2026-05-02T12:06:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/accel-ppp/accel-ppp.git/commit/?id=8ee09f05d15276b295ea199f08fb3bc2e2d16121'/>
<id>urn:sha1:8ee09f05d15276b295ea199f08fb3bc2e2d16121</id>
<content type='text'>
Recently i wasted several hours searching bug in workflows/userspace.
Turned out in dmesg we had highly visible WARNING that we dont watch.

After each test run, dump dmesg and grep for canonical kernel-issue
markers (WARNING, BUG, Oops, kernel panic, GPF, KASAN, kernel UBSAN,
soft/hard lockup, hung tasks, bad page state, invalid opcode). Fail
the job if any are present, with a GitHub Actions error annotation.

Until now, kernel WARNs from out-of-tree drivers (e.g. vlan_mon
tripping the new ETH_P_ALL ptype_head WARN_ON in 6.6+) were silently
swallowed by the existing 'Display processes and dmesg after tests'
steps -- visible only if a human inspected the log. The check runs
with if: always() so it triggers both on test failure and on test
completion.

Applied to all four workflows that load kernel modules:
run-tests-asan-ubsan.yml, run-tests.yml (Test-in-Qemu, Test-in-Alpine,
Test-in-GH, Test-in-GH-Coverage), run-tests-32bit.yml, and
run-tests-bigendian.yml.

P.S. Some whitespace churn included.

Signed-off-by: Denys Fedoryshchenko &lt;denys.f@collabora.com&gt;
</content>
</entry>
<entry>
<title>ci: update alpine links</title>
<updated>2024-12-11T00:36:32+00:00</updated>
<author>
<name>Sergey V. Lobanov</name>
<email>sergey@lobanov.in</email>
</author>
<published>2024-12-11T00:36:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/accel-ppp/accel-ppp.git/commit/?id=6350ca6af999605b9474b9efe013657c4802de2b'/>
<id>urn:sha1:6350ca6af999605b9474b9efe013657c4802de2b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ci: fix build on alpine BE (s390x)</title>
<updated>2024-11-28T22:05:58+00:00</updated>
<author>
<name>Sergey V. Lobanov</name>
<email>sergey@lobanov.in</email>
</author>
<published>2024-11-28T20:44:11+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/accel-ppp/accel-ppp.git/commit/?id=90982f7e5c46905c3f72cfdffb1d6051a93c1fa6'/>
<id>urn:sha1:90982f7e5c46905c3f72cfdffb1d6051a93c1fa6</id>
<content type='text'>
bump libpcre, disable chap_secrets in tests
</content>
</entry>
<entry>
<title>ci: run tests on alpine s390x (big-endian)</title>
<updated>2024-08-26T21:36:47+00:00</updated>
<author>
<name>Sergey V. Lobanov</name>
<email>sergey@lobanov.in</email>
</author>
<published>2024-08-26T21:23:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/accel-ppp/accel-ppp.git/commit/?id=636657f530ec70f913e73521075af5bfff15f170'/>
<id>urn:sha1:636657f530ec70f913e73521075af5bfff15f170</id>
<content type='text'>
s390x is the only big-endian platform supported by major Linux vendors.
Alpine s390x is the only major distro that includes pppoe kernel module.
Ubuntu, Debian, RHEL (and Fedora) removed pppoe from kernel config so
alpine s390x is used. Alpine doesn't provide cloud-image for s390x that
is why netboot installed is used.

It is almost zero probability that someone will run accel-ppp on s390x
IBM mainframe, but testing on big-endian platform is useful for another
platforms (e.g. mips-be and ppc-be which is still in use on home gateways
and supported by openwrt).
</content>
</entry>
</feed>
