Hi,
On 19-05-2024 2:55 p.m., 陈 晟祺 wrote:
My concern now is that the results do not seem to be stable or reproducible.
That's an reoccurring problem in lots of places, yes.
Is there any convention in handling such situation? E.g., should I mark all
zfs-test-suite-x
as flaky and treat them
Hi,
> 2024年5月19日 13:51，Paul Gevers 写道：
>
> I already noticed yesterday and had it run; it failed. (Currently) top one
> here: https://ci.debian.net/packages/z/zfs-linux/testing/amd64/
>
My concern now is that the results do not seem to be stable or reproducible.
Seven tests have been run
Hi
On 19-05-2024 6:25 a.m., 陈 晟祺 wrote:
I have made more adjustments, basically skipping some flaky tests in VM.
Now new version 2.2.4-1 is in the archive, please try that again when available.
I already noticed yesterday and had it run; it failed. (Currently) top
one here:
Hi,
>
> The test ran. Unfortunately zfs-test-suite-1 failed.
>
I have made more adjustments, basically skipping some flaky tests in VM.
Now new version 2.2.4-1 is in the archive, please try that again when available.
Thanks,
Shengqi Chen
Hi,
On 18-04-2024 10:25 p.m., Paul Gevers wrote:
I'll hopefully do the changes tomorrow. (RL work is a bit busy at the
moment.)
The test ran. Unfortunately zfs-test-suite-1 failed.
https://ci.debian.net/packages/z/zfs-linux/unstable/amd64/45683824/
4089s Results Summary
4089s PASS 681
Hi,
On 14-04-2024 5:14 a.m., 陈 晟祺 wrote:
I would have aron to review & upload a new version, then we can test on
debci infra and see whether it solves the problem.
I forgot I promised changes to the settings. Without those changes, it
doesn't end nicely:
Hi,
On 14-04-2024 5:14 a.m., 陈 晟祺 wrote:
When using non-ramdisk tmpdir (/var/tmp) and some large tests skipped [1],
the tests would run with 2 core + 4GB memory + ~10GB disk space.
I also tried 2GB / 3GB, and both will be interrupted by OOM killer.
So, let's settle on 2+4 for now. That sounds
Control: tags -1 + pending
Hi,
> 2024年4月13日 01:29，陈 晟祺 写道：
>
> I am now trying to run tests on 2 core and 4GB memory (and maybe less later).
> If the tester itself does not occupy too much RAM, the real requirement for
> resources
> is now probably several gigabytes of disk space (currently
Hi,
> 2024年4月12日 12:48，Paul Gevers 写道：
>
> Hi,
>
> On 12-04-2024 4:42 a.m., 陈 晟祺 wrote:
>> - If I limit the test file size to 1G, quite many tests would fail even with
>> adequate resources
>
> Ack. To be fair, I was more thinking to make current test conditional on the
> available free
Hi,
On 12-04-2024 4:42 a.m., 陈 晟祺 wrote:
- If I limit the test file size to 1G, quite many tests would fail even with
adequate resources
Ack. To be fair, I was more thinking to make current test conditional on
the available free disk space. But yeah, that might also lead to issues
as the
Hi,
> 2024年4月12日 02:39，Paul Gevers 写道：
>
> Hi
>
> On 11-04-2024 5:18 p.m., 陈 晟祺 wrote:
>> If possible, could you help to build with latest code on salsa then run
>> autopkgtest again on a normal debci VM?
>
> As I'm doing this live on the infrastructure, I don't want to do anything
> there
Hi
On 11-04-2024 5:18 p.m., 陈 晟祺 wrote:
If possible, could you help to build with latest code on salsa then run
autopkgtest again on a normal debci VM?
As I'm doing this live on the infrastructure, I don't want to do
anything there except testing what's in the archive, sorry.
My private
Hi Paul,
2024年4月11日 20:59，Paul Gevers 写道：
Hi,
With the default size of the ramdisk and 2 cpu's the test crashes with:
Test: /usr/share/zfs/zfs-tests/tests/functional/large_files/setup (run as root)
[00:00] [PASS]
Test: /usr/share/zfs/zfs-tests/tests/functional/large_files/large_files_001_pos
Hi,
With the default size of the ramdisk and 2 cpu's the test crashes with:
Test: /usr/share/zfs/zfs-tests/tests/functional/large_files/setup (run
as root) [00:00] [PASS]
Test:
/usr/share/zfs/zfs-tests/tests/functional/large_files/large_files_001_pos
(run as root) [00:00] [PASS]
Test:
Hi,
Some additional info from my side.
I have just run the following:
root@ci-worker13:~# /usr/bin/autopkgtest --no-built-binaries
--test-name=zfs-test-suite --timeout-factor=3 --user debci zfs-linux --
qemu --cpus=2 --ram-size=8192 /var/lib/debci/qemu/testing-amd64.img
The test failed and
Hi,
Some additional information and errata here.
I have split the tests into four stanzas as upstream does [1].
The resources of one GitHub Action runner is actually 4 cores + 16GB memory, not
2 cores + 8GB as I mentioned before. The test could finish within reasonable
time (3hrs)
with such
Hi,
> 2024年4月9日 02:51，Paul Gevers 写道：
>
> Our timeout is 1 seconds, so 2.47 hours, per autopkgtest stanza (overall
> it's 8 hours). If the test is going to take longer, it will fail anyways. So
> maybe it was just still running? I'm a bit hesitant, particularly about the
> memory to make
Hi,
On 08-04-2024 3:51 a.m., 陈 晟祺 wrote:
With resources limited to one CPU (AMD EPYC 7551) and 2G memory,
my local test could now reproduce the test hang and following time out error.
Ouch.
I think it is caused by insufficient resources (e.g. OOM killer, but I am not
sure).
Even we can
Hi Paul,
> 2024年4月7日 21:10，Paul Gevers 写道：
>
> Hi,
>
> The host that runs this is an m3-large instance at equinix [1].
>
> We create the qemu image with autopkgtest-build-qemu (default settings as far
> as I know).
>
> From within the testbed:
> root@host:~# lscpu
> lscpu
> Architecture:
Hi,
On 07-04-2024 2:29 p.m., 陈 晟祺 wrote:
Could you please provide more detailed information on the test settings on
ci.d.o.?
E.g., CPU type, #cores, memory size, etc.
The host that runs this is an m3-large instance at equinix [1].
We create the qemu image with autopkgtest-build-qemu
Hi,
> 2024年4月7日 17:23，Paul Gevers 写道：
>
> Dear maintainer(s),
>
> Your package has an autopkgtest, great. I recently added support for
> isolation-machine tests on ci.debian.net for amd64 and added your package to
> the list to use that. However, it fails because the zfs-test-suite test
Source: zfs-linux
Version: 2.2.3-1
Severity: important
User: debian...@lists.debian.org
Usertags: isolation-machine timeout
Dear maintainer(s),
Your package has an autopkgtest, great. I recently added support for
isolation-machine tests on ci.debian.net for amd64 and added your
package to the
22 matches
Mail list logo
