Hello All,
The Jenkins server will stop processing jobs tonight around 22:00 UTC in
order to shutdown the server. This downtime is needed to peform an upgrade
of Jenkins.
Start: 2024-03-25 22:00 UTC
End: 2024-03-26 02:00 UTC
Regards,
--
Kelley Spoon <kelley.spoon(a)linaro.org>
Greetings All,
The Jenkins server on ci.linaro.org will stop accepting new jobs in a few
moments and will be shutdown around 6pm UTC today. The reason for this
downtime is perform an upgrade to the server to address a CVE advisory in
the current release.
Regards,
--
Kelley Spoon <kelley.spoon(a)linaro.org>
Hello All,
The Jenkins server will stop processing jobs on 2024-1-13 at around 3:00pm
UTC as the server will be put into "Shutdown mode".
Afterwards the server will be in a maintenance window from 4:00pm UTC until
12:00am UTC in order to preform upgrades on Jenkins and the host OS.
Start: 2024-1-13 16:00 UTC
End: 2024-1-14 00:00 UTC
Regards,
--
Kelley Spoon <kelley.spoon(a)linaro.org>
Hi Bash Experts!
Every couple of years I stumble upon weird behavior in bash scripts, which I cannot explain, and every time it was due to documented bash behavior. Can, please, someone explain to me why the following script terminates?
I've tried this on Ubuntu 22.04 and Ubuntu 20.04 with same results -- see "Observations" at the end of the script.
Thanks!
===
#!/bin/bash
set -euf -o pipefail
print_test ()
{
local count="$1"
while [ $count -ge 0 ]; do
if [ x"$(echo a)" = x"a" ]; then
echo a
fi
count=$(($count - 1))
done
}
main ()
{
local count=1
while print_test "$count" | grep -q "a"; do
echo "$count: OK"
count=$(($count + 1))
done
echo "$count: BAD"
}
main
exit 1
# Observations:
# 1. With "if" in print_test BAD happens on around count "2"
# 2. Without "if" in print_test BAD happens around count "80"
# 3. Changing "grep -q" to "grep" makes the problem go away.
# 4. Removing -o pipefail makes the problem go away.
# 5. While loop in "main" isn't required, but makes reproduction easier.
===
--
Maxim Kuvyrkov
https://www.linaro.org
Hello All,
The Jenkins server will stop processing jobs on the 2022-12-09 at around
<21:00> UTC, as the server will be put into "Shutdown mode".
This downtime is needed in order to upgrade Jenkins and some of
its plugins.
Start: 2022-12-09 22:00 UTC
End: 2022-12-10 02:00 UTC
Regards,
--
Kelley Spoon <kelley.spoon(a)linaro.org>
Hi,
First of all, please ignore this email if you are NOT a Marvell's
MACCHIATOBin user.
If you are, I hope you can help me :)
I'm trying to install a NIC card into a PCIe slot on MACCHIATOBin DoubleSlot,
but the kernel hangs up during the boot. What I found out so far is
scanning a PCIe bus and initializing the controller or the device
may have caused this error. When I trace the kernel execution by
inserting debug messages, access to a control register on PCIe controller
has caused a CPU to stall forever:
=== details ===
armada8k_pcie_probe()
armada8k_add_pcie_port()
dw_pcie_host_init()
dw_pcie_host_init()
dw_pcie_setup_rc()
dw_pcie_dbi_ro_wr_en() -- inline
reg = PCIE_MISC_CONTROL_1_OFF;
val = dw_pcie_readl_dbi(pci, reg) <= here
=== ===
The same code, the same kernel, does work without any errors
if a given NIC card (Intel i225) is not inserted in a slot.
My current environment is:
TF-A: mainline v2.7
SCP_BL2: HEAD of https://github.com/MarvellEmbeddedProcessors/binaries-marvell.git
mv-ddr: HEAD of https://github.com/MarvellEmbeddedProcessors/mv-ddr-marvell.git
U-Boot: u-boot-2020.10-release of https://github.com/MarvellEmbeddedProcessors/u-boot-marvell.git
OS: Debian 11 with the kernel v5.17 (from unstable release)
(but the problem exists even with v5.10 of bullseye.)
So I would like to ask you,
1) Have you ever seen this sort of error in your experience?
2) If possible, please try to use a PCIe card on your board.
3) Then, please let me know your result along with your environment
(software that you are using)
Will be much appreciated.
-Takahiro Akashi
Hello All,
The Jenkins server will be rebooted today in order to perform
an upgrade to the next point release 2.332.3.
This upgrade is needed to address a dead lock issue that is
causing jobs to pile up in the queue.
Start: 2022-05-06 21:00 UTC
End: 2022-05-06 23:00 UTC
Apologies for the short notice.
Regards,
--
Kelley Spoon <kelley.spoon(a)linaro.org>
Hello All,
The server will stop processing jobs on 2022-04-15 at around
16:00 UTC, as the server will be put into "Shutdown mode".
This downtime is needed in order to upgrade Jenkins and some of
its plugins.
Notable change:
As of 2.307, Jenkins will begin a naming migration to refer to the "master"
node as "built-in". We have submitted updates to existing jobs that request
"master" as the build node to add in the "built-in" label and will continue
to support "master" as a label on the new server.
Start: 2022-04-16 12:00 UTC
End: 2022-04-16 20:00 UTC
--
Kelley Spoon <kelley.spoon(a)linaro.org>
