Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEST-35-LOGIN is flaky in Github Actions #32698

Closed
DaanDeMeyer opened this issue May 7, 2024 · 0 comments · Fixed by #32884
Closed

TEST-35-LOGIN is flaky in Github Actions #32698

DaanDeMeyer opened this issue May 7, 2024 · 0 comments · Fixed by #32884
Labels
bug 🐛 Programming errors, that need preferential fixing tests

Comments

@DaanDeMeyer
Copy link
Contributor

systemd version the issue has been seen with

main

Used distribution

No response

Linux kernel version used

No response

CPU architectures issue was seen on

None

Component

No response

Expected behaviour you didn't see

No response

Unexpected behaviour you saw

https://github.com/systemd/systemd/actions/runs/8988213589/job/24688525012?pr=32681

Test Journal: https://github.com/systemd/systemd/actions/runs/8988213589/artifacts/1481011621

Steps to reproduce the problem

No response

Additional program output to the terminal or log subsystem illustrating the issue

23/57 systemd:integration-tests / TEST-35-LOGIN                 FAIL             19.95s   exit status 1
>>> MALLOC_PERTURB_=151 SYSTEMD_INTEGRATION_TESTS=1 /home/runner/work/systemd/systemd/test/integration-test-wrapper.py --meson-source-dir /home/runner/work/systemd/systemd --meson-build-dir /mnt/mkosi/build --test-name TEST-35-LOGIN --test-number 35 --storage volatile --firmware linux --
――――――――――――――――――――――――――――――――――――― ✀  ―――――――――――――――――――――――――――――――――――――
Listing only the last 100 lines from a long log.
[   10.278067] testsuite-35.sh[718]: + systemctl daemon-reload
[   10.645475] testsuite-35.sh[718]: + systemctl restart [email protected]
[   10.721848] testsuite-35.sh[718]: + for i in {1..30}
[   10.724561] testsuite-35.sh[718]: + ((  i > 1  ))
[   10.725906] testsuite-35.sh[718]: + check_session
[   10.731799] testsuite-35.sh[753]: + set +ex
[   10.733124] testsuite-35.sh[753]: no session or multiple sessions for logind-test-user.
[   10.735905] testsuite-35.sh[718]: + for i in {1..30}
[   10.737828] testsuite-35.sh[718]: + ((  i > 1  ))
[   10.741525] testsuite-35.sh[718]: + sleep 1
[   11.739162] testsuite-35.sh[718]: + check_session
[   11.740949] testsuite-35.sh[793]: + set +ex
[   11.785324] testsuite-35.sh[718]: + break
[   11.786323] testsuite-35.sh[718]: + check_session
[   11.790343] testsuite-35.sh[814]: + set +ex
[   11.830343] testsuite-35.sh[835]: ++ loginctl --no-legend
[   11.834243] testsuite-35.sh[836]: ++ grep -v manager
[   11.836286] testsuite-35.sh[837]: ++ awk '$3=="logind-test-user" { print $7 }'
[   11.842765] testsuite-35.sh[718]: + assert_eq tty2 tty2
[   11.844738] testsuite-35.sh[838]: + set +ex
[   11.846497] testsuite-35.sh[840]: ++ loginctl --no-legend
[   11.850422] testsuite-35.sh[841]: ++ grep -v manager
[   11.852459] testsuite-35.sh[842]: ++ awk '$3 == "logind-test-user" { print $1 }'
[   11.857914] testsuite-35.sh[718]: + loginctl activate 3
[   11.866963] testsuite-35.sh[845]: ++ loginctl list-sessions --no-legend
[   11.868499] testsuite-35.sh[846]: ++ grep -v manager
[   11.870372] testsuite-35.sh[847]: ++ awk '$3 == "logind-test-user" { print $1 }'
[   11.874841] testsuite-35.sh[718]: + session=3
[   11.876024] testsuite-35.sh[718]: + : check that we got a valid session id
[   11.877704] testsuite-35.sh[718]: + busctl get-property org.freedesktop.login1 /org/freedesktop/login1/session/_33 org.freedesktop.login1.Session Id
[   11.884978] testsuite-35.sh[848]: s "3"
[   11.886971] testsuite-35.sh[850]: ++ loginctl list-sessions --no-legend
[   11.888794] testsuite-35.sh[852]: ++ awk '$3 == "logind-test-user" { print $2 }'
[   11.893208] testsuite-35.sh[851]: ++ grep -v manager
[   11.896241] testsuite-35.sh[853]: ++ id -ru logind-test-user
[   11.898143] testsuite-35.sh[718]: + assert_eq 4712 4712
[   11.900187] testsuite-35.sh[854]: + set +ex
[   11.902463] testsuite-35.sh[856]: ++ loginctl list-sessions --no-legend
[   11.905994] testsuite-35.sh[857]: ++ grep -v manager
[   11.907725] testsuite-35.sh[858]: ++ awk '$3 == "logind-test-user" { print $4 }'
[   11.914031] testsuite-35.sh[718]: + seat=seat0
[   11.917789] testsuite-35.sh[860]: ++ loginctl list-sessions --no-legend
[   11.920257] testsuite-35.sh[861]: ++ grep -v manager
[   11.921809] testsuite-35.sh[862]: ++ awk '$3 == "logind-test-user" { print $6 }'
[   11.925429] testsuite-35.sh[718]: + assert_eq user user
[   11.927897] testsuite-35.sh[863]: + set +ex
[   11.930257] testsuite-35.sh[865]: ++ loginctl list-sessions --no-legend
[   11.932865] testsuite-35.sh[866]: ++ grep -v manager
[   11.935540] testsuite-35.sh[867]: ++ awk '$3 == "logind-test-user" { print $7 }'
[   11.948287] testsuite-35.sh[718]: + assert_eq tty2 tty2
[   11.950147] testsuite-35.sh[868]: + set +ex
[   11.951715] testsuite-35.sh[870]: ++ loginctl list-sessions --no-legend
[   11.953903] testsuite-35.sh[871]: ++ grep -v manager
[   11.956822] testsuite-35.sh[872]: ++ awk '$3 == "logind-test-user" { print $8 }'
[   11.960237] testsuite-35.sh[718]: + assert_eq no no
[   11.961737] testsuite-35.sh[873]: + set +ex
[   11.967052] testsuite-35.sh[875]: ++ loginctl list-sessions --no-legend
[   11.973908] testsuite-35.sh[876]: ++ grep -v manager
[   11.979609] testsuite-35.sh[877]: ++ awk '$3 == "logind-test-user" { print $9 }'
[   11.985387] testsuite-35.sh[718]: + assert_eq - -
[   11.989443] testsuite-35.sh[878]: + set +ex
[   11.993165] testsuite-35.sh[879]: + loginctl list-seats --no-legend
[   11.998153] testsuite-35.sh[880]: + grep -Fwq seat0
[   12.002513] testsuite-35.sh[882]: ++ loginctl list-users --no-legend
[   12.007728] testsuite-35.sh[883]: ++ awk '$2 == "logind-test-user" { print $1 }'
[   12.013682] testsuite-35.sh[884]: ++ id -ru logind-test-user
[   12.018306] testsuite-35.sh[718]: + assert_eq 4712 4712
[   12.022774] testsuite-35.sh[885]: + set +ex
[   12.026428] testsuite-35.sh[887]: ++ loginctl list-users --no-legend
[   12.033891] testsuite-35.sh[888]: ++ awk '$2 == "logind-test-user" { print $3 }'
[   12.041678] testsuite-35.sh[718]: + assert_eq no no
[   12.048660] testsuite-35.sh[889]: + set +ex
[   12.051234] testsuite-35.sh[891]: ++ loginctl list-users --no-legend
[   12.053506] testsuite-35.sh[892]: ++ awk '$2 == "logind-test-user" { print $4 }'
[   12.055862] testsuite-35.sh[718]: + assert_eq active active
[   12.057715] testsuite-35.sh[893]: + set +ex
[   12.059140] testsuite-35.sh[718]: + loginctl enable-linger logind-test-user
[   12.061185] testsuite-35.sh[896]: ++ loginctl list-users --no-legend
[   12.063232] testsuite-35.sh[897]: ++ awk '$2 == "logind-test-user" { print $3 }'
[   12.065363] testsuite-35.sh[718]: + assert_eq yes yes
[   12.067089] testsuite-35.sh[898]: + set +ex
[   12.068416] testsuite-35.sh[900]: ++ loginctl list-sessions --no-legend
[   12.070396] testsuite-35.sh[902]: ++ awk '$3 == "logind-test-user" { print $1 }'
[   12.072521] testsuite-35.sh[901]: ++ grep tty
[   12.073993] testsuite-35.sh[718]: + for s in $(loginctl list-sessions --no-legend | grep tty | awk '$3 == "logind-test-user" { print $1 }')
[   12.079236] testsuite-35.sh[718]: + loginctl terminate-session 3
[   12.081062] testsuite-35.sh[718]: + timeout 30 bash -c 'while loginctl --no-legend | grep tty | grep -q logind-test-user; do sleep 1; done'
[   13.114926] testsuite-35.sh[925]: ++ loginctl list-users --no-legend
[   13.126917] testsuite-35.sh[926]: ++ awk '$2 == "logind-test-user" { print $4 }'
[   13.149565] testsuite-35.sh[718]: + assert_eq online lingering
[   13.152872] testsuite-35.sh[927]: + set +ex
[   13.154450] testsuite-35.sh[927]: FAIL: expected: 'lingering' actual: 'online'
[   13.166601] testsuite-35.sh[572]: + cleanup_test_user
[   13.169621] testsuite-35.sh[928]: + set +ex
@DaanDeMeyer DaanDeMeyer added bug 🐛 Programming errors, that need preferential fixing tests labels May 7, 2024
yuwata added a commit to yuwata/systemd that referenced this issue May 17, 2024
If a session in closing state, the user state will be in online.

Fixes systemd#32698.
DaanDeMeyer pushed a commit that referenced this issue May 17, 2024
If a session in closing state, the user state will be in online.

Fixes #32698.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🐛 Programming errors, that need preferential fixing tests
Development

Successfully merging a pull request may close this issue.

1 participant