Not so fast it seems, I just got this:
```
+++ /srv/rpmtests.dir/at-groups/353/stderr 2024-04-04 08:40:58.419002150
+
@@ -1,2 +1,2 @@
-error: Illegal char '*' (0x2a) in: *
+error: failed to write all data to /tmp/bad.req: Broken pipe
```
But at least it's now hinting at the problem.
Reopened #2470.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2470#event-12354300211
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing
Closing in favor of #2949, seems fairly obvious this is the same issue.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2470#issuecomment-1980968956
You are receiving this because you are subscribed to this thread.
Message ID:
Closed #2470 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2470#event-12028572241
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint
Oh, gotcha. Yep, in that case, Ubuntu can be eliminated for sure now :smile:
Whether or not I was running the tests through podman + bwrap or just bwrap is
another matter but Ubuntu was *not* involved at all, yup :smile:
--
Reply to this email directly or view it on GitHub:
It was originally spotted with fakechroot and Semaphore of course, but that was
still a Fedora container running on top of Ubuntu. Getting it locally
eliminates Ubuntu from the picture (unless you've switched to the dark side
:laughing: ) but we now have continers locally too. Okay there was
Wasn't the first encounter with the fakechroot backend and in the Semaphore CI
though?
Anyway, I *think* this last one I saw was actually on the "native" backend that
uses bwrap (but I'm not entirely sure as I'm currently tweaking all this as
part of #2643 :smile: )
--
Reply to this email
I have a feeling there's a connection between our first local instance of this
failure and switching over to containers. Which backend was it on?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2470#issuecomment-1733379875
You are
Just FTR, I just got this failure *locally* so apparently it's not limited to
the CI/Ubuntu environment.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2470#issuecomment-1725217697
You are receiving this because you are subscribed to
Then there's the intermittent failure with bwrap's mounting table parsing that
we discussed in the chat. I'm thinking we should have a Known issues sections
somewhere (in the tests/README perhaps) listing these. I'll probably add that
later.
--
Reply to this email directly or view it on
What's common between the previous SemaphoreCI setup and the current GH Actions
one is that we 1) run in an Ubuntu VM (18.04 -> 22.04) and 2) we run in a
Docker container. My guess would be the latter (Docker) causing this but we yet
have to figure it out :smile:
--
Reply to this email
Still happening after switching to GH Actions. But I'm quite certain I've never
seen this locally.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2470#issuecomment-1672993076
You are receiving this because you are subscribed to this
It's worth noting that the bug is not the error message but the lack of it, and
a weird return code.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2470#issuecomment-1532697211
You are receiving this because you are subscribed to this
13 matches
Mail list logo
