mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #3928] CI seems broken, unsure on how to proceed. #2460
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#2460
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Jan 30, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3928
I'm seeing Build
CI/ build_and_test (pull_request)failuresin the last 2 PR's (#3924 and #3926). The PR's in question seem to be rather straightforward profile changes and I'm not familiar enough with that part of the process to easilly spot what could be wrong by looking at the CI logs. Just putting this out here to bring it to the attention of more experienced collaborators.Personally I think it's wise to temporarily stop merging until the CI situation clears up, no matter how irritating this could be for people wanting to contribute.
@rusty-snake commented on GitHub (Jan 30, 2021):
Since
7c1dae04every BuildCI fails (sort.py continues to work). But I don't understand how this is possible. I already searched for telegram, error, fail in the logs, but I saw nothing relevant.@rusty-snake commented on GitHub (Jan 30, 2021):
I just re-run the BuildCI for
f806d340(the last commit where is passed) and it failed. Seems to be caused by a cahnge in GitHub Actions?@reinerh commented on GitHub (Jan 30, 2021):
One of the tests related to sound is now failing. No idea why it was working before, or why it's now failing:
@reinerh commented on GitHub (Jan 30, 2021):
In
environment.shthere is a check if aplay exists. Only then this test is actually run.Maybe the github CI environment now contains aplay (even though there is no soundcard), so the test fails.
I'll improve the check.