Comments (7)
Test Report
from release-specs.
The LoRaWAN failure was expected, as RIOT-OS/RIOT#18745 is not yet backported (and not even merged yet).
from release-specs.
The LoRaWAN failure was expected, as RIOT-OS/RIOT#18745 is not yet backported (and not even merged yet).
Nope, that fix does not have anything for that (according to @jia200x it is only about the dedicated tests/driver_*
tests for those devices). The lorawan examples should still work, but there was a flashing error:
11-lorawan.test_spec11
Test case: | test_task01[nodes0] |
---|---|
Outcome: | Failed |
Duration: | 43.141 sec |
Failed | subprocess.CalledProcessError: Command '['make', '--no-print-directory', '-C', '/home/runner/work/RIOT/RIOT/RIOT/examples/lorawan', 'flash']' returned non-zero exit status 2. |
riot_ctrl = <function riot_ctrl.<locals>.ctrl at 0x7f320083c040> ttn_client = <testutils.ttn.TTNClient object at 0x7f320059e760> @pytest.mark.iotlab_creds # nodes passed to riot_ctrl fixture @pytest.mark.parametrize( "nodes", [pytest.param(["b-l072z-lrwan1"])], indirect=["nodes"] ) def test_task01(riot_ctrl, ttn_client): > node = riot_ctrl(0, LORAWAN_APP, ShellInteraction) 11-lorawan/test_spec11.py:83: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ conftest.py:369: in ctrl node.make_run( .tox/test/lib/python3.8/site-packages/riotctrl/ctrl.py:193: in make_run return subprocess.run(command, env=self.env, *runargs, **runkwargs) _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ input = None, capture_output = False, timeout = None, check = True popenargs = (['make', '--no-print-directory', '-C', '/home/runner/work/RIOT/RIOT/RIOT/examples/lorawan', 'flash'],) kwargs = {'env': {'APPEUI': '0000000000000000', 'APPKEY': '782D212CE97434EAB523EA7F98A70F52', 'APPSKEY': '2F4E8084C26812D4E95DE48305B65BC9', 'BOARD': 'b-l072z-lrwan1', ...}, 'stderr': None, 'stdout': None} process = <subprocess.Popen object at 0x7f32008849a0>, stdout = None stderr = None, retcode = 2 def run(*popenargs, input=None, capture_output=False, timeout=None, check=False, **kwargs): """Run command with arguments and return a CompletedProcess instance. The returned instance will have attributes args, returncode, stdout and stderr. By default, stdout and stderr are not captured, and those attributes will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture them. If check is True and the exit code was non-zero, it raises a CalledProcessError. The CalledProcessError object will have the return code in the returncode attribute, and output & stderr attributes if those streams were captured. If timeout is given, and the process takes too long, a TimeoutExpired exception will be raised. There is an optional argument "input", allowing you to pass bytes or a string to the subprocess's stdin. If you use this argument you may not also use the Popen constructor's "stdin" argument, as it will be used internally. By default, all communication is in bytes, and therefore any "input" should be bytes, and the stdout and stderr will be bytes. If in text mode, any "input" should be a string, and stdout and stderr will be strings decoded according to locale encoding, or by "encoding" if set. Text mode is triggered by setting any of text, encoding, errors or universal_newlines. The other arguments are the same as for the Popen constructor. """ if input is not None: if kwargs.get('stdin') is not None: raise ValueError('stdin and input arguments may not both be used.') kwargs['stdin'] = PIPE if capture_output: if kwargs.get('stdout') is not None or kwargs.get('stderr') is not None: raise ValueError('stdout and stderr arguments may not be used ' 'with capture_output.') kwargs['stdout'] = PIPE kwargs['stderr'] = PIPE with Popen(*popenargs, **kwargs) as process: try: stdout, stderr = process.communicate(input, timeout=timeout) except TimeoutExpired as exc: process.kill() if _mswindows: # Windows accumulates the output in a single blocking # read() call run on child threads, with the timeout # being done in a join() on those threads. communicate() # _after_ kill() is required to collect that and add it # to the exception. exc.stdout, exc.stderr = process.communicate() else: # POSIX _communicate already populated the output so # far into the TimeoutExpired exception. process.wait() raise except: # Including KeyboardInterrupt, communicate handled that. process.kill() # We don't call process.wait() as .__exit__ does that for us. raise retcode = process.poll() if check and retcode: > raise CalledProcessError(retcode, process.args, output=stdout, stderr=stderr) E subprocess.CalledProcessError: Command '['make', '--no-print-directory', '-C', '/home/runner/work/RIOT/RIOT/RIOT/examples/lorawan', 'flash']' returned non-zero exit status 2. /opt/hostedtoolcache/Python/3.8.14/x64/lib/python3.8/subprocess.py:516: CalledProcessError
--------------------------------- Captured Log ------------------------------------------------------------------ Captured Out ---------------------------------
Launching build container using image "docker.io/riot/riotbuild:latest".
docker run --rm --tty --user $(id -u) -v '/usr/share/zoneinfo/Etc/UTC:/etc/localtime:ro' -v '/home/runner/work/RIOT/RIOT/RIOT:/data/riotbuild/riotbase:delegated' -v '/home/runner/.cargo/registry:/data/riotbuild/.cargo/registry:delegated' -v '/home/runner/.cargo/git:/data/riotbuild/.cargo/git:delegated' -e 'RIOTBASE=/data/riotbuild/riotbase' -e 'CCACHE_BASEDIR=/data/riotbuild/riotbase' -e 'BUILD_DIR=/data/riotbuild/riotbase/build' -e 'RIOTPROJECT=/data/riotbuild/riotbase' -e 'RIOTCPU=/data/riotbuild/riotbase/cpu' -e 'RIOTBOARD=/data/riotbuild/riotbase/boards' -e 'RIOTMAKE=/data/riotbuild/riotbase/makefiles' -e 'QUIETER=1' -e 'DEVEUI=70B3D57ED00463E7' -e 'APPEUI=0000000000000000' -e 'APPKEY=782D212CE97434EAB523EA7F98A70F52' -e 'BOARD=b-l072z-lrwan1' -e 'IOTLAB_NODE=st-lrwan1-11.saclay.iot-lab.info' -e 'DISABLE_MODULE=' -e 'DEFAULT_MODULE=' -e 'FEATURES_REQUIRED=' -e 'FEATURES_BLACKLIST=' -e 'FEATURES_OPTIONAL=periph_rtc' -e 'USEMODULE=auto_init_loramac fmt sx1276' -e 'USEPKG=semtech-loramac' -w '/data/riotbuild/riotbase/examples/lorawan/' 'docker.io/riot/riotbuild:latest' make -j
#x1B[1;32mBuilding application "lorawan" for "b-l072z-lrwan1" with MCU "stm32".#x1B[0mtext data bss dec hex filename
56184 328 6340 62852 f584 /data/riotbuild/riotbase/examples/lorawan/bin/b-l072z-lrwan1/lorawan.elf
iotlab-node --jmespath='keys(@)[0]' --format='lambda ret: exit(int(ret))' --id 340908 --list saclay,st-lrwan1,11 --flash /home/runner/work/RIOT/RIOT/RIOT/examples/lorawan/bin/b-l072z-lrwan1/lorawan.bin
--------------------------------- Captured Err --------------------------------- make: *** [/home/runner/work/RIOT/RIOT/RIOT/Makefile.include:838: flash] Error 1
from release-specs.
For many of the problems with https://github.com/RIOT-OS/RIOT/actions/runs/3250328677 (test-on-iotlab) (which help cover 1.1, 2.1-3 and 99) RIOT-OS/RIOT#18722 will help.
from release-specs.
heavy_multiplication_x 11. Task 02 - OTAA join procedure ** FAILED **
heavy_multiplication_x 11. Task 03 - ABP join procedure ** FAILED **
Failed now, but succeeded in the last run.
from release-specs.
I re-triggered spec 11 task02 and task03 and it succeeded. See https://github.com/RIOT-OS/RIOT/actions/runs/3311670065/jobs/5467395615
from release-specs.
Closing in favor of #264
from release-specs.
Related Issues (20)
- Release 2022.04 - RC4 HOT 11
- Release 2022.04 - RC5 HOT 2
- Release 2022.04 - RC6 HOT 28
- Release 2022.04 - RC7 HOT 3
- Rust: describe that crate versions should be bent away from git
- Release 2022.07 - RC1 HOT 16
- Release 2022.07 - RC2 HOT 4
- Release 2022.07 - RC3 HOT 7
- Release 2022.07 - RC4 HOT 25
- Release 2022.10 - RC2 HOT 9
- Release 2022.10 - RC3 HOT 18
- Release 2023.01 - RC1 HOT 3
- Release 2023.01 - RC2 HOT 2
- Release 2023.01 - RC3 HOT 14
- 08 - Task 11: Building zephyr on atsamr21_xpro not possible HOT 4
- Release 2023.04 - RC1 HOT 12
- [RFC] Restructure/update Release Specs HOT 2
- Release 2023.04 - RC2 HOT 5
- Release 2023.04 - RC3 HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from release-specs.