Hung meta-arm build
Richard Purdie
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/1579
On the worker (opensuse152-ty-1): pstree -p shows: ├─Cooker(30044)─┬─Worker(5328)─┬─nativesdk-perl:(44339)───run.do_compile.(47448)───make(47505)───make(41311)─┬─make(47131)───true(387) │ │ │ └─make(48106)───true(48776) │ │ └─{Worker}(5476) │ ├─pseudo(19403)───Worker (Fakeroo(19419)───{Worker (Fakeroo}(20828) │ └─{Cooker}(34065) and the state of the indvidual processes: pokybuild@opensuse152-ty-1:~> ps ax | grep XXX 387 ? ZN 0:00 [true] <defunct> 48776 ? ZN 0:00 [true] <defunct> 47131 ? SN 0:00 make -C cpan/Unicode-Collate/ all PERL_CORE=1 LIBPERL=libperl.so.5.34.0 LINKTYPE=dynamic 48106 ? SN 0:00 make -C ext/I18N-Langinfo/ all PERL_CORE=1 LIBPERL=libperl.so.5.34.0 LINKTYPE=dynamic 47505 ? SN 0:00 make -j 16 -l 52 47448 ? SN 0:00 /bin/sh /home/pokybuild/yocto-worker/meta-arm/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-perl/5.34.0-r0/temp/run.do_compile.44339 so it looks like a make deadlock? :/ Cheers, Richard
|
|
bitbake-worker failure traceback
Richard Purdie
I saw:
https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/2167 failed and logged in the grab the cookerdaemon log whilst they were still there. In the log there was the traceback: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/qemux86-world-alt/build/bitbake/bin/bitbake-worker", line 513, in <module> worker.serve() File "/home/pokybuild/yocto-worker/qemux86-world-alt/build/bitbake/bin/bitbake-worker", line 402, in serve self.handle_item(b"newtaskhashes", self.handle_newtaskhashes) File "/home/pokybuild/yocto-worker/qemux86-world-alt/build/bitbake/bin/bitbake-worker", line 420, in handle_item func(self.queue[(len(item) + 2):index]) File "/home/pokybuild/yocto-worker/qemux86-world-alt/build/bitbake/bin/bitbake-worker", line 444, in handle_newtaskhashes self.workerdata["newhashes"] = pickle.loads(data) _pickle.UnpicklingError: invalid load key, '\x00'. invalid load key, '\x00'./home/pokybuild/yocto-worker/qemux86-world-alt/build/bitbake/lib/bb/runqueue.py:1329: ResourceWarning: unclosed file <_io.BufferedWriter name=131> self.worker = {} Not sure why that could happen but it is helpful to have the data and we could maybe improve that exception handling to dump the invalid data so the next time it happens we get further info. Cheers, Richard
|
|
Re: musl-qemux86: do_compile_kernelmodules() failed
Michael Halstead <mhalstead@...>
Yes, after the tmp directories were filled and we had inode exhaustion I changed the tmpfiles.d configuration to delete tmp files immediately. I expected this to happen on boot only but it also happens once every day. I've changed settings to only remove files 3 days old or older. No builds last over 3 days so I expect this will fix the problem.
On Mon, Oct 4, 2021 at 5:24 AM Richard Purdie <richard.purdie@...> wrote: Yes, it seems we have a problem on Centos 8 where files in /tmp are being --
Michael Halstead Linux Foundation / Yocto Project Systems Operations Engineer
|
|
centos8 failure summary
Richard Purdie
Hi,
I tried to summarise all of the "/tmp" file issues we've seen. We have 4 of them, 3 on centos8-ty-2 and one on centos8-ty-1. Issues seen once in python code, twice in kernel modules in the assembler and once in automake over an m4 file. No idea what is going on :( Cheers, Richard centos8-ty-1 oe-selftest pseudo.Pseudo.test_pseudo_pyc_creation https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2644/steps/14/logs/stdio NOTE: Running task 7 of 8 (/tmp/devtoolqa7t333xgr/core-copy/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb:do_install) ERROR: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/bin/bitbake-worker", line 253, in child the_data = bb_cache.loadDataFull(fn, appends) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/lib/bb/cache.py", line 332, in loadDataFull bb_data = self.load_bbfile(virtualfn, appends, virtonly=True) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/lib/bb/cache.py", line 345, in load_bbfile datastores = parse_recipe(bb_data, bbfile, appends, mc) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/lib/bb/cache.py", line 308, in parse_recipe bb_data = bb.parse.handle(bbfile, bb_data) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/lib/bb/parse/__init__.py", line 107, in handle return h['handle'](fn, data, include) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/lib/bb/parse/parse_py/BBHandler.py", line 114, in handle abs_fn = resolve_file(fn, d) File "/home/pokybuild/yocto-worker/oe-selftest-centos/build/bitbake/lib/bb/parse/__init__.py", line 131, in resolve_file raise IOError(errno.ENOENT, "file %s not found" % fn) FileNotFoundError: [Errno 2] file /tmp/devtoolqa7t333xgr/core-copy/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb not found ERROR: Task (/tmp/devtoolqa7t333xgr/core-copy/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb:do_install) failed with exit code '1' centos8-ty-2 reproducible-centos https://autobuilder.yoctoproject.org/typhoon/#/builders/115/builds/766 /home/pokybuild/yocto-worker/reproducible-centos/build/meta/recipes-kernel/linux/linux-yocto_5.14.bb:do_compile_kernelmodules /home/pokybuild/yocto-worker/reproducible-centos/build/meta/recipes-core/dbus/dbus_1.12.20.bb:do_configure | CC [M] fs/nls/nls_cp737.o | Assembler messages: | Error: can't open /tmp/ccUONJmc.s for reading: No such file or directory | make[3]: *** [/home/pokybuild/yocto-worker/reproducible-centos/build/build-st/reproducibleA/tmp/work-shared/qemux86-64/kernel-source/scripts/Makefile.build:271: fs/nls/nls_cp737.o] Error 1 | autoreconf: running: /home/pokybuild/yocto-worker/reproducible-centos/build/build-st/reproducibleA/tmp/work/core2-64-poky-linux/dbus/1.12.20-r0/recipe-sysroot-native/usr/bin/autoconf --include=/home/pokybuild/yocto-worker/reproducible-centos/build/build-st/reproducibleA/tmp/work/core2-64-poky-linux/dbus/1.12.20-r0/dbus-1.12.20/m4/ --include=/home/pokybuild/yocto-worker/reproducible-centos/build/build-st/reproducibleA/tmp/work/core2-64-poky-linux/dbus/1.12.20-r0/recipe-sysroot-native/usr/share/aclocal/ --force | autom4te: error: cannot open /tmp/arGZ1Myy/am4tld4nPo/traces.m4: No such file or directory | autoreconf: error: /home/pokybuild/yocto-worker/reproducible-centos/build/build-st/reproducibleA/tmp/work/core2-64-poky-linux/dbus/1.12.20-r0/recipe-sysroot-native/usr/bin/autoconf failed with exit status: 1 musl-qemux86 centos8-ty-2 https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4099/steps/11/logs/stdio | Assembler messages: | Error: can't open /tmp/ccQzs5nT.s for reading: No such file or directory | make[3]: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/scripts/Makefile.build:271: drivers/net/tun.o] Error 1
|
|
Re: musl-qemux86: do_compile_kernelmodules() failed
Richard Purdie
Yes, it seems we have a problem on Centos 8 where files in /tmp are being
toggle quoted messageShow quoted text
removed unexpectedly for unknown reasons and causing a variety of build failures. Michael: Were there any recent changes in the updates to the Centos 8 system that would explain this? Cheers, Richard
On Mon, 2021-10-04 at 09:00 +0000, Naveen Saini wrote:
It seems CentOS specific !
|
|
Re: musl-qemux86: do_compile_kernelmodules() failed
Naveen Saini
It seems CentOS specific !
Same kernelmodules() failure during reproducible-centos: https://autobuilder.yoctoproject.org/typhoon/#/builders/115/builds/766
And oe-selftest-centos failures too only on centos: https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2644
Regards, Naveen
From: swat@... <swat@...>
On Behalf Of Naveen Saini
Hi Richard,
On master-next, do_compile_kernelmodules() is failing (with musl).
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4099
Error log:
| Assembler messages: | Error: can't open /tmp/ccQzs5nT.s for reading: No such file or directory | make[3]: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/scripts/Makefile.build:271: drivers/net/tun.o] Error 1 | make[2]: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/scripts/Makefile.build:514: drivers/net] Error 2 | make[1]: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/Makefile:1858: drivers] Error 2 | make: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/Makefile:220: __sub-make] Error 2 | make: Leaving directory '/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/linux-qemux86-standard-build' | ERROR: oe_runmake failed | WARNING: /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957:220 exit 1 from 'exit 1' | WARNING: Backtrace (BB generated script): | #1: bbfatal_log, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 220 | #2: die, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 204 | #3: oe_runmake, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 199 | #4: do_compile_kernelmodules, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 170 | #5: main, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 223 NOTE: recipe linux-yocto-5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0: task do_compile_kernelmodules: Failed ERROR: Task (/home/pokybuild/yocto-worker/musl-qemux86/build/meta/recipes-kernel/linux/linux-yocto_5.14.bb:do_compile_kernelmodules) failed with exit code '1'
Regards, Naveen
|
|
musl-qemux86: do_compile_kernelmodules() failed
Naveen Saini
Hi Richard,
On master-next, do_compile_kernelmodules() is failing (with musl).
https://autobuilder.yoctoproject.org/typhoon/#/builders/64/builds/4099
Error log:
| Assembler messages: | Error: can't open /tmp/ccQzs5nT.s for reading: No such file or directory | make[3]: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/scripts/Makefile.build:271: drivers/net/tun.o] Error 1 | make[2]: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/scripts/Makefile.build:514: drivers/net] Error 2 | make[1]: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/Makefile:1858: drivers] Error 2 | make: *** [/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work-shared/qemux86/kernel-source/Makefile:220: __sub-make] Error 2 | make: Leaving directory '/home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/linux-qemux86-standard-build' | ERROR: oe_runmake failed | WARNING: /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957:220 exit 1 from 'exit 1' | WARNING: Backtrace (BB generated script): | #1: bbfatal_log, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 220 | #2: die, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 204 | #3: oe_runmake, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 199 | #4: do_compile_kernelmodules, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 170 | #5: main, /home/pokybuild/yocto-worker/musl-qemux86/build/build/tmp/work/qemux86-poky-linux-musl/linux-yocto/5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0/temp/run.do_compile_kernelmodules.1482957, line 223 NOTE: recipe linux-yocto-5.14.6+gitAUTOINC+42d2cf670e_7ae156be3b-r0: task do_compile_kernelmodules: Failed ERROR: Task (/home/pokybuild/yocto-worker/musl-qemux86/build/meta/recipes-kernel/linux/linux-yocto_5.14.bb:do_compile_kernelmodules) failed with exit code '1'
Regards, Naveen
|
|
Re: The postinstall intercept hook failures on master-next
Naveen Saini
It is happening again on master now, for most builds: https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2685
Regards, Naveen
From: swat@... <swat@...>
On Behalf Of Naveen Saini
Hi Richard,
I can see a number of postinstall intercept hook failures on master-next on oe-selftest builds on all distros and reproducible builds.
Error log: do_rootfs: The postinstall intercept hook 'update_pixbuf_cache' failed
do_rootfs: The postinstall intercept hook 'update_font_cache' failed
do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed
do_rootfs: The postinstall intercept hook 'update_udev_hwdb' failed
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2678
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/2646 https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2636 https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/2617 https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/2611
I already raised a bug for 'update_udev_hwdb' https://bugzilla.yoctoproject.org/show_bug.cgi?id=14583
I can not see more logs to look deeper, should I raise bugs for all of them ?
Regards, Naveen
|
|
Re: YP Autobuilder/SwatBoart Enhancement
Alexandre Belloni
On 01/10/2021 12:52:46+0000, Naveen Saini wrote:
Ahh..right !! Thanks.I agree, this would meake it easier and I'm not dismissing the idea but it is not simple to implement in the current architecture. Let's leave it open and discuss on Thursday Regards,-- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
|
Re: YP Autobuilder/SwatBoart Enhancement
Naveen Saini
Ahh..right !! Thanks.
toggle quoted messageShow quoted text
But still I think, in case of build cancellation, this provision can make debugging easier. If still this does not make much sense, I can close this bug. Regards, Naveen
-----Original Message-----
|
|
Re: YP Autobuilder/SwatBoart Enhancement
Alexandre Belloni
Hello,
On 01/10/2021 09:02:07+0000, Naveen Saini wrote: Hi Team,I explained on https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team how to get that: $ git clone git://git.yoctoproject.org/poky $ cd poky $ git fetch origin 47482eff9897ccde946e9247724babc3a586d318 $ git log FETCH_HEAD This should work unless the git garbage collector ran. -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
|
YP Autobuilder/SwatBoart Enhancement
Naveen Saini
Hi Team,
I created a bug#14584 to enhance Autobuilder/SwatBoat process. https://bugzilla.yoctoproject.org/show_bug.cgi?id=14584
Description: Currently when user cancel a build, there is no provision to enter reason, why it was cancelled. If there is no need to triage such cancelled builds then allow to enable 'Not for SWAT'
Sometime it becomes difficult to analyse the build failures, when mater-next branch is force rebased (drop conflict patch). In that case, there is no way to know which commits were included in cancelled builds.
Regards, Naveen
|
|
The postinstall intercept hook failures on master-next
Naveen Saini
Hi Richard,
I can see a number of postinstall intercept hook failures on master-next on oe-selftest builds on all distros and reproducible builds.
Error log: do_rootfs: The postinstall intercept hook 'update_pixbuf_cache' failed
do_rootfs: The postinstall intercept hook 'update_font_cache' failed
do_rootfs: The postinstall intercept hook 'update_gio_module_cache' failed
do_rootfs: The postinstall intercept hook 'update_udev_hwdb' failed
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2678
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/2646 https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/2636 https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/2617 https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/2611
I already raised a bug for 'update_udev_hwdb' https://bugzilla.yoctoproject.org/show_bug.cgi?id=14583
I can not see more logs to look deeper, should I raise bugs for all of them ?
Regards, Naveen
|
|
Re: SWAT Rotation schedule
Naveen Saini
Acknowledged.
toggle quoted messageShow quoted text
Regards, Naveen
-----Original Message-----
|
|
Re: SWAT Rotation schedule
Alexandre Belloni
Hello Naveen,
toggle quoted messageShow quoted text
It is a quick reminder that you will be on SWAT duty starting Friday October 1st.
On 16/09/2021 23:29:50+0200, Alexandre Belloni wrote:
Hello, --
Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
|
Re: SWAT Rotation schedule
Alexandre Belloni
On 23/09/2021 05:15:06+0000, Oleksiy Obitotskyy via lists.yoctoproject.org wrote:
Hi,Thanks, there are currently 7 failures that are not triaged. The two reproducible issues may already be fixed and we'll know that once the nightly builds have finished. Unfortunately, the logs for the qemuarm64 failure are already gone are there is already a (failing) qemuarm64 build running on the same worker. The four other ones are one off issues that didn't repeat, I'll discuss with Richard what to do with them. Regards, -- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
|
Re: SWAT Rotation schedule
Hi,
I will start as planned from 24/09/2021. Regards, Oleksiy ________________________________________ From: swat@... <swat@...> on behalf of Alexandre Belloni <alexandre.belloni@...> Sent: Friday, September 17, 2021 00:29 To: Alejandro Hernandez Samaniego; swat@... Subject: [swat] SWAT Rotation schedule Hello, Following the summer break, I would like to organize SWAT duty rotation. This time, I've prepared a semi randomized schedule so it is easier for each one of you to plan for SWAT duty. Please check the table and let me know if you are not available for the selected week. SWAT duty will be from Friday to Thursday and the goal is to triage all the failures on swatbot before the weekly triage call happening at 2:30pm UTC. ┌──────┬────────────┐ │ Week │ Start │ ┌───────────────────────────────┼──────┼────────────┤ │ Alejandro Hernandez Samaniego │ 37 │ 17/09/2021 │ │ Oleksiy Obitotskyy │ 38 │ 24/09/2021 │ │ Naveen Saini │ 39 │ 01/10/2021 │ │ Thomas Perrot │ 40 │ 08/10/2021 │ │ Paul Eggleton │ 41 │ 15/10/2021 │ │ Christopher Larson │ 42 │ 22/10/2021 │ │ Jon Mason │ 43 │ 29/10/2021 │ │ Lee Chee Yang │ 44 │ 05/11/2021 │ │ Minjae Kim │ 45 │ 12/11/2021 │ │ Jaga │ 46 │ 19/11/2021 │ │ Leo Sandoval │ 47 │ 26/11/2021 │ │ Ross Burton │ 48 │ 03/12/2021 │ │ Köry Maincent │ 49 │ 10/12/2021 │ │ Anibal Limon │ 50 │ 17/12/2021 │ │ Saul Wold │ 51 │ 24/12/2021 │ └───────────────────────────────┴──────┴────────────┘ Alejandro you would be the next one on the list, starting this Friday, can you confirm you are available? There are currently 8 failures to triage on swatbot, I'm going to take care of those. Thanks! -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
|
Re: [EXTERNAL] [swat] SWAT Rotation schedule
Alejandro Hernandez Samaniego
Hello Alex,
Sadly I'm not available this week, I apologize for the late reply but I've been out, can you reschedule me for a different week?
Alejandro
|
|
Re: SWAT Rotation schedule
Alexandre Belloni
On 17/09/2021 08:55:10-0700, Saul Wold wrote:
Sure, I realize that and I was thinking probably there will be less builds at that time anyway! Sau!--┌──────┬────────────┐-- Alexandre Belloni, co-owner and COO, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
|
|
Re: SWAT Rotation schedule
Saul Wold
On 9/16/21 2:29 PM, Alexandre Belloni wrote:
Hello,Hi Alexandre, Great work on creating a schedule that might be more predictable! Just a heads up, the date you have me is right over the Christmas break. I am not saying drop me as I might be working anyway, but when things get closer I will let you know if I have other plans (going skiing!). Sau! ┌──────┬────────────┐-- Sau!
|
|