* tests/avocado/machine_s390_ccw_virtio: Fedora test failing
@ 2022-11-15 11:03 Philippe Mathieu-Daudé
2022-11-15 11:05 ` Thomas Huth
0 siblings, 1 reply; 7+ messages in thread
From: Philippe Mathieu-Daudé @ 2022-11-15 11:03 UTC (permalink / raw)
To: Cornelia Huck, Thomas Huth
Cc: QEMU Developers, open list:S390 general arch...
Hi,
As of v7.2.0-rc0 I am getting:
(101/198)
tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora:
FAIL (23.51 s)
$ cat
test-results/101-tests_avocado_machine_s390_ccw_virtio.py_S390CCWVirtioMachine.test_s390x_fedora/debug.log
01:20:44 INFO | INIT 1-S390CCWVirtioMachine.test_s390x_fedora
01:20:44 DEBUG| PARAMS (key=timeout, path=*, default=120) => 120
01:20:44 DEBUG| Test metadata:
01:20:44 DEBUG| filename:
/builddir/qemu/tests/avocado/machine_s390_ccw_virtio.py
01:20:44 DEBUG| teststmpdir: /tmp/avocado_ccw348hc
01:20:44 DEBUG| workdir:
/tmp/tmp2qg0mcch/test-results/tmp_dirkh7k2yra/1-S390CCWVirtioMachine.test_s390x_fedora
01:20:44 INFO | START 1-S390CCWVirtioMachine.test_s390x_fedora
01:20:44 DEBUG| DATA (filename=output.expected) => NOT FOUND (data
sources: variant, test, file)
01:20:44 DEBUG| PARAMS (key=arch, path=*, default=s390x) => 's390x'
01:20:44 DEBUG| PARAMS (key=cpu, path=*, default=None) => None
01:20:44 DEBUG| PARAMS (key=qemu_bin, path=*,
default=./qemu-system-s390x) => './qemu-system-s390x'
01:20:44 DEBUG| PARAMS (key=machine, path=*, default=s390-ccw-virtio) =>
's390-ccw-virtio'
01:20:46 DEBUG| QEMUMachine "default" created
01:20:46 DEBUG| QEMUMachine "default" temp_dir:
/tmp/tmp2qg0mcch/test-results/tmp_dirkh7k2yra/1-S390CCWVirtioMachine.test_s390x_fedora/qemu-machine-da4ubla3
01:20:46 DEBUG| QEMUMachine "default" log_dir:
/tmp/tmp2qg0mcch/test-results/1-S390CCWVirtioMachine.test_s390x_fedora
01:21:05 INFO | Test whether QEMU CLI options have been considered
01:21:06 INFO | Test screendump of virtio-gpu device
01:21:07 ERROR|
01:21:07 ERROR| Reproduced traceback from:
/builddir/qemu/tests/venv/lib/python3.10/site-packages/avocado/core/test.py:772
01:21:07 ERROR| Traceback (most recent call last):
01:21:07 ERROR| File
"/builddir/qemu/tests/venv/lib/python3.10/site-packages/avocado/core/decorators.py",
line 90, in wrapper
01:21:07 ERROR| return function(obj, *args, **kwargs)
01:21:07 ERROR| File
"/builddir/qemu/tests/avocado/machine_s390_ccw_virtio.py", line 256, in
test_s390x_fedora
01:21:07 ERROR| self.assertEqual(line, b"The quick fox jumps over a
lazy dog\n")
01:21:07 ERROR| File
"/opt/homebrew/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py",
line 845, in assertEqual
01:21:07 ERROR| assertion_func(first, second, msg=msg)
01:21:07 ERROR| File
"/opt/homebrew/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py",
line 838, in _baseAssertEqual
01:21:07 ERROR| raise self.failureException(msg)
01:21:07 ERROR| AssertionError:
b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\[979 chars]\x00' != b'The
quick fox jumps over a lazy dog\n'
01:21:07 ERROR|
01:21:07 DEBUG| Local variables:
01:21:07 DEBUG| -> obj <class
'machine_s390_ccw_virtio.S390CCWVirtioMachine'>:
1-S390CCWVirtioMachine.test_s390x_fedora
01:21:07 DEBUG| -> args <class 'tuple'>: ()
01:21:07 DEBUG| -> kwargs <class 'dict'>: {}
01:21:07 DEBUG| -> condition <class 'NoneType'>: None
01:21:07 DEBUG| -> function <class 'function'>: <function
S390CCWVirtioMachine.test_s390x_fedora at 0x1063b1990>
01:21:07 DEBUG| -> message <class 'str'>: Running on GitLab
01:21:07 DEBUG| -> negate <class 'bool'>: False
01:21:07 ERROR| FAIL 1-S390CCWVirtioMachine.test_s390x_fedora ->
AssertionError: b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\[979
chars]\x00' != b'The quick fox jumps over a lazy dog\n'
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing 2022-11-15 11:03 tests/avocado/machine_s390_ccw_virtio: Fedora test failing Philippe Mathieu-Daudé @ 2022-11-15 11:05 ` Thomas Huth 2022-11-15 11:13 ` Philippe Mathieu-Daudé 0 siblings, 1 reply; 7+ messages in thread From: Thomas Huth @ 2022-11-15 11:05 UTC (permalink / raw) To: Philippe Mathieu-Daudé, Cornelia Huck Cc: QEMU Developers, open list:S390 general arch... On 15/11/2022 12.03, Philippe Mathieu-Daudé wrote: > Hi, > > As of v7.2.0-rc0 I am getting: > > (101/198) > tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: > FAIL (23.51 s) Is it 100% reproducible? ... the test is known to be a little bit shaky, that's also why it is disabled in the gitlab CI. Thomas ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing 2022-11-15 11:05 ` Thomas Huth @ 2022-11-15 11:13 ` Philippe Mathieu-Daudé 2022-11-16 9:43 ` Thomas Huth 0 siblings, 1 reply; 7+ messages in thread From: Philippe Mathieu-Daudé @ 2022-11-15 11:13 UTC (permalink / raw) To: Thomas Huth, Cornelia Huck Cc: QEMU Developers, open list:S390 general arch... On 15/11/22 12:05, Thomas Huth wrote: > On 15/11/2022 12.03, Philippe Mathieu-Daudé wrote: >> Hi, >> >> As of v7.2.0-rc0 I am getting: >> >> (101/198) >> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (23.51 s) > > Is it 100% reproducible? ... the test is known to be a little bit shaky, > that's also why it is disabled in the gitlab CI. I am running it on my workstation, not GitLab. (1/2) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_devices: PASS (7.69 s) (2/2) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (23.07 s) (1/2) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_devices: PASS (6.63 s) (2/2) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (24.27 s) (1/2) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_devices: PASS (5.39 s) (2/2) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (24.23 s) (1/2) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_devices: PASS (6.65 s) (2/2) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (23.55 s) 5/5 failures. I'll skip it locally (no need to send a patch) and we can have a look after the release. Regards, Phil. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing 2022-11-15 11:13 ` Philippe Mathieu-Daudé @ 2022-11-16 9:43 ` Thomas Huth 2022-11-16 10:23 ` Philippe Mathieu-Daudé 0 siblings, 1 reply; 7+ messages in thread From: Thomas Huth @ 2022-11-16 9:43 UTC (permalink / raw) To: Philippe Mathieu-Daudé, Cornelia Huck Cc: QEMU Developers, open list:S390 general arch... On 15/11/2022 12.13, Philippe Mathieu-Daudé wrote: > On 15/11/22 12:05, Thomas Huth wrote: >> On 15/11/2022 12.03, Philippe Mathieu-Daudé wrote: >>> Hi, >>> >>> As of v7.2.0-rc0 I am getting: >>> >>> (101/198) >>> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: >>> FAIL (23.51 s) >> >> Is it 100% reproducible? ... the test is known to be a little bit shaky, >> that's also why it is disabled in the gitlab CI. > > I am running it on my workstation, not GitLab. I just double-checked and for me, it's working fine an my laptop, with both, rc0 and rc1. > 5/5 failures. I'll skip it locally (no need to send a patch) and we can > have a look after the release. If it is a real bug, we should fix it before the release. Could you maybe bisect it, please? Also, what do you get when dumping the console? I.e.: ./tests/venv/bin/avocado --show=console run -t arch:s390x \ tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora ? Thanks, Thomas ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing 2022-11-16 9:43 ` Thomas Huth @ 2022-11-16 10:23 ` Philippe Mathieu-Daudé 2022-11-16 10:58 ` Thomas Huth 0 siblings, 1 reply; 7+ messages in thread From: Philippe Mathieu-Daudé @ 2022-11-16 10:23 UTC (permalink / raw) To: Thomas Huth Cc: QEMU Developers, Cornelia Huck, open list:S390 general arch..., Cleber Rosa, Beraldo Leal, Jan Richter Cc'ing Jan/Cleber/Beraldo. On 16/11/22 10:43, Thomas Huth wrote: > On 15/11/2022 12.13, Philippe Mathieu-Daudé wrote: >> On 15/11/22 12:05, Thomas Huth wrote: >>> On 15/11/2022 12.03, Philippe Mathieu-Daudé wrote: >>>> Hi, >>>> >>>> As of v7.2.0-rc0 I am getting: >>>> >>>> (101/198) >>>> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (23.51 s) >>> >>> Is it 100% reproducible? ... the test is known to be a little bit >>> shaky, that's also why it is disabled in the gitlab CI. >> >> I am running it on my workstation, not GitLab. > > I just double-checked and for me, it's working fine an my laptop, with > both, rc0 and rc1. > >> 5/5 failures. I'll skip it locally (no need to send a patch) and we can >> have a look after the release. > > If it is a real bug, we should fix it before the release. Could you > maybe bisect it, please? > > Also, what do you get when dumping the console? I.e.: > > ./tests/venv/bin/avocado --show=console run -t arch:s390x \ > tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora When running with the current (old) Avocado runner I get: Avocado crashed: TypeError: cannot pickle '_thread.RLock' object Please include the traceback info and command line used on your bug report Report bugs visiting https://github.com/avocado-framework/avocado/issues/new I can use the 'new' runner: $ TMPDIR=/tmp ./tests/venv/bin/avocado --show=app,console run --test-runner=nrunner -t arch:s390x tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora JOB ID : 2e62ee88c4f04926281f31ab696f4cd4703612f5 JOB LOG : /Users/philmd/avocado/job-results/job-2022-11-16T11.05-2e62ee8/job.log (1/1) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: STARTED (1/1) tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (24.63 s) RESULTS : PASS 0 | ERROR 0 | FAIL 1 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0 JOB TIME : 25.16 s but I'm almost blind: I don't get any console output. The only useful info I found is closer to stderr: $ cat /Users/philmd/avocado/job-results/job-2022-11-16T11.05-2e62ee8//test-results/1-tests_avocado_machine_s390_ccw_virtio.py_S390CCWVirtioMachine.test_s390x_fedora/debug.log 11:05:20 INFO | INIT 1-S390CCWVirtioMachine.test_s390x_fedora 11:05:20 DEBUG| PARAMS (key=timeout, path=*, default=120) => 120 11:05:20 DEBUG| Test metadata: 11:05:20 DEBUG| filename: /Users/philmd/source/qemu/build/tests/avocado/machine_s390_ccw_virtio.py 11:05:20 DEBUG| teststmpdir: /tmp/avocado_zswqnw_l 11:05:20 DEBUG| workdir: /tmp/tmppq8l13fn/test-results/tmp_dir2cjl2nd2/1-S390CCWVirtioMachine.test_s390x_fedora 11:05:20 INFO | START 1-S390CCWVirtioMachine.test_s390x_fedora 11:05:20 DEBUG| DATA (filename=output.expected) => NOT FOUND (data sources: variant, test, file) 11:05:20 DEBUG| PARAMS (key=arch, path=*, default=s390x) => 's390x' 11:05:20 DEBUG| PARAMS (key=cpu, path=*, default=None) => None 11:05:20 DEBUG| PARAMS (key=qemu_bin, path=*, default=./qemu-system-s390x) => './qemu-system-s390x' 11:05:20 DEBUG| PARAMS (key=machine, path=*, default=s390-ccw-virtio) => 's390-ccw-virtio' 11:05:22 DEBUG| QEMUMachine "default" created 11:05:22 DEBUG| QEMUMachine "default" temp_dir: /tmp/tmppq8l13fn/test-results/tmp_dir2cjl2nd2/1-S390CCWVirtioMachine.test_s390x_fedora/qemu-machine-di5d3r66 11:05:22 DEBUG| QEMUMachine "default" log_dir: /tmp/tmppq8l13fn/test-results/1-S390CCWVirtioMachine.test_s390x_fedora 11:05:40 INFO | Test whether QEMU CLI options have been considered 11:05:41 INFO | Test screendump of virtio-gpu device 11:05:44 ERROR| 11:05:44 ERROR| Reproduced traceback from: /Users/philmd/source/qemu/build/tests/venv/lib/python3.10/site-packages/avocado/core/test.py:772 11:05:44 ERROR| Traceback (most recent call last): 11:05:44 ERROR| File "/Users/philmd/source/qemu/build/tests/venv/lib/python3.10/site-packages/avocado/core/decorators.py", line 90, in wrapper 11:05:44 ERROR| return function(obj, *args, **kwargs) 11:05:44 ERROR| File "/Users/philmd/source/qemu/build/tests/avocado/machine_s390_ccw_virtio.py", line 256, in test_s390x_fedora 11:05:44 ERROR| self.assertEqual(line, b"The quick fox jumps over a lazy dog\n") 11:05:44 ERROR| File "/opt/homebrew/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 845, in assertEqual 11:05:44 ERROR| assertion_func(first, second, msg=msg) 11:05:44 ERROR| File "/opt/homebrew/Cellar/python@3.10/3.10.8/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual 11:05:44 ERROR| raise self.failureException(msg) 11:05:44 ERROR| AssertionError: b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\[979 chars]\x00' != b'The quick fox jumps over a lazy dog\n' 11:05:44 ERROR| 11:05:44 DEBUG| Local variables: 11:05:44 DEBUG| -> obj <class 'machine_s390_ccw_virtio.S390CCWVirtioMachine'>: 1-S390CCWVirtioMachine.test_s390x_fedora 11:05:44 DEBUG| -> args <class 'tuple'>: () 11:05:44 DEBUG| -> kwargs <class 'dict'>: {} 11:05:44 DEBUG| -> condition <class 'NoneType'>: None 11:05:44 DEBUG| -> function <class 'function'>: <function S390CCWVirtioMachine.test_s390x_fedora at 0x1030d1990> 11:05:44 DEBUG| -> message <class 'str'>: Running on GitLab 11:05:44 DEBUG| -> negate <class 'bool'>: False 11:05:44 ERROR| FAIL 1-S390CCWVirtioMachine.test_s390x_fedora -> AssertionError: b'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\[979 chars]\x00' != b'The quick fox jumps over a lazy dog\n' 11:05:44 INFO | IIUC Cleber should post a series soon upgrading the QEMU Avocado framework to use the 'new' runner. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing 2022-11-16 10:23 ` Philippe Mathieu-Daudé @ 2022-11-16 10:58 ` Thomas Huth 2022-11-16 11:12 ` Philippe Mathieu-Daudé 0 siblings, 1 reply; 7+ messages in thread From: Thomas Huth @ 2022-11-16 10:58 UTC (permalink / raw) To: Philippe Mathieu-Daudé Cc: QEMU Developers, Cornelia Huck, open list:S390 general arch..., Cleber Rosa, Beraldo Leal, Jan Richter On 16/11/2022 11.23, Philippe Mathieu-Daudé wrote: > Cc'ing Jan/Cleber/Beraldo. > > On 16/11/22 10:43, Thomas Huth wrote: >> On 15/11/2022 12.13, Philippe Mathieu-Daudé wrote: >>> On 15/11/22 12:05, Thomas Huth wrote: >>>> On 15/11/2022 12.03, Philippe Mathieu-Daudé wrote: >>>>> Hi, >>>>> >>>>> As of v7.2.0-rc0 I am getting: >>>>> >>>>> (101/198) >>>>> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: >>>>> FAIL (23.51 s) >>>> >>>> Is it 100% reproducible? ... the test is known to be a little bit shaky, >>>> that's also why it is disabled in the gitlab CI. >>> >>> I am running it on my workstation, not GitLab. >> >> I just double-checked and for me, it's working fine an my laptop, with >> both, rc0 and rc1. >> >>> 5/5 failures. I'll skip it locally (no need to send a patch) and we can >>> have a look after the release. >> >> If it is a real bug, we should fix it before the release. Could you maybe >> bisect it, please? >> >> Also, what do you get when dumping the console? I.e.: >> >> ./tests/venv/bin/avocado --show=console run -t arch:s390x \ >> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora >> > > When running with the current (old) Avocado runner I get: > > Avocado crashed: TypeError: cannot pickle '_thread.RLock' object > Please include the traceback info and command line used on your bug report > Report bugs visiting https://github.com/avocado-framework/avocado/issues/new > > I can use the 'new' runner: > > $ TMPDIR=/tmp ./tests/venv/bin/avocado --show=app,console run > --test-runner=nrunner -t arch:s390x Uh, don't do that. nrunner does not seem to be able to execute that test yet. Or did you also upgrade your avocado to a newer installation? ... in that case it sounds like you might have messed up your installation? Maybe try again with a fresh and clean checkout of the QEMU repository / a new build folder. Thomas ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: tests/avocado/machine_s390_ccw_virtio: Fedora test failing 2022-11-16 10:58 ` Thomas Huth @ 2022-11-16 11:12 ` Philippe Mathieu-Daudé 0 siblings, 0 replies; 7+ messages in thread From: Philippe Mathieu-Daudé @ 2022-11-16 11:12 UTC (permalink / raw) To: Thomas Huth Cc: QEMU Developers, Cornelia Huck, open list:S390 general arch..., Cleber Rosa, Beraldo Leal, Jan Richter On 16/11/22 11:58, Thomas Huth wrote: > On 16/11/2022 11.23, Philippe Mathieu-Daudé wrote: >> Cc'ing Jan/Cleber/Beraldo. >> >> On 16/11/22 10:43, Thomas Huth wrote: >>> On 15/11/2022 12.13, Philippe Mathieu-Daudé wrote: >>>> On 15/11/22 12:05, Thomas Huth wrote: >>>>> On 15/11/2022 12.03, Philippe Mathieu-Daudé wrote: >>>>>> Hi, >>>>>> >>>>>> As of v7.2.0-rc0 I am getting: >>>>>> >>>>>> (101/198) >>>>>> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora: FAIL (23.51 s) >>>>> >>>>> Is it 100% reproducible? ... the test is known to be a little bit >>>>> shaky, that's also why it is disabled in the gitlab CI. >>>> >>>> I am running it on my workstation, not GitLab. >>> >>> I just double-checked and for me, it's working fine an my laptop, >>> with both, rc0 and rc1. >>> >>>> 5/5 failures. I'll skip it locally (no need to send a patch) and we can >>>> have a look after the release. >>> >>> If it is a real bug, we should fix it before the release. Could you >>> maybe bisect it, please? >>> >>> Also, what do you get when dumping the console? I.e.: >>> >>> ./tests/venv/bin/avocado --show=console run -t arch:s390x \ >>> tests/avocado/machine_s390_ccw_virtio.py:S390CCWVirtioMachine.test_s390x_fedora >> >> When running with the current (old) Avocado runner I get: >> >> Avocado crashed: TypeError: cannot pickle '_thread.RLock' object >> Please include the traceback info and command line used on your bug >> report >> Report bugs visiting >> https://github.com/avocado-framework/avocado/issues/new >> >> I can use the 'new' runner: >> >> $ TMPDIR=/tmp ./tests/venv/bin/avocado --show=app,console run >> --test-runner=nrunner -t arch:s390x > > Uh, don't do that. nrunner does not seem to be able to execute that test > yet. Or did you also upgrade your avocado to a newer installation? ... > in that case it sounds like you might have messed up your installation? > Maybe try again with a fresh and clean checkout of the QEMU repository / > a new build folder. Well the current (old) runner doesn't work on Darwin ARM64: Avocado crashed: TypeError: cannot pickle '_thread.RLock' object Using `TMPDIR=/tmp avocado --test-runner=nrunner` almost all other tests pass. I'll wait for Cleber's nrunner update before re-testing/bisecting. ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2022-11-16 11:13 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2022-11-15 11:03 tests/avocado/machine_s390_ccw_virtio: Fedora test failing Philippe Mathieu-Daudé 2022-11-15 11:05 ` Thomas Huth 2022-11-15 11:13 ` Philippe Mathieu-Daudé 2022-11-16 9:43 ` Thomas Huth 2022-11-16 10:23 ` Philippe Mathieu-Daudé 2022-11-16 10:58 ` Thomas Huth 2022-11-16 11:12 ` Philippe Mathieu-Daudé
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).