Age | Commit message (Collapse) | Author |
|
.. to rewrite with latest changes in noise computation
Only these 4 jobs to avoid big amount of rewrite time.
Change-Id: I86dc8ed6e54f35a2c2056271749d9866a947f96f
|
|
... non-existent machine.
Change-Id: I3470cf25fa49b26febe061e3b1bf363d1803ca9d
|
|
This patch improves survivability of flaky entries in base-artifacts
history. It improves handling of the following scenario:
1. Trim_base_artifacts() has removed some really old "non-forced"
history entries, say, from 6 months ago. With it, it removed
a 6-month-old flaky entry.
2. We trigger re-write of history for some good reason.
3. A "non-forced" entry from 5 months ago no longer passes because
it is missing a flaky entry from the removed revision -- note
the time difference between removed 6-month old entry and this
5-month old entry is within flaky active period.
4. The "non-forced" entry from 5 months ago is removed. With it,
it removed a 5-month-old flaky entry.
5. And so on into the present time.
It appears that we can mitigate the above behavior by adding more
flaky entries to the "forced" history entries. E.g., we could stop
passing known flaky list to ABE in "forced" builds -- this will
make ABE work hard to re-detect as many flaky tests as possible.
These flaky entries will then remain in history forever because
of update_baseline==force setting.
Change-Id: Ie6bf3e0058a10f316a5cfd45dcf6bf5dbec474f9
|
|
Change-Id: I5bdc225c4b18fc87e8a2cb6b058470b29266525e
|
|
... to handle corrupted results in "forced" history entry.
See Change-Id: Id6b3abbf9904ab2ddb041a683b11c405e053e5b9
for the related commit.
Change-Id: I3c9744a0b352508bbc184d55f9bc8582c682ffb8
|
|
Change-Id: I2ef91f49dd0b50a03790ed7ce7d7363b397f333e
|
|
Change-Id: I6afbf8e68d2413ed8f6e4c901042b2863c9f4b18
|
|
While re-writing result history for
tcwg_gnu_native_fast_check_gcc--master-aarch64
we have detected a corrupted sumfiles/xfails.xfail file,
which previous versions of validate_failures.py happened
to accept. Current version of validate_failures.py complains
on this result, and we need to remove this result from the history.
We are going to do this by failing with $EXTERNAL_FAIL when
validate_failures.py can't process results.
Change-Id: Id6b3abbf9904ab2ddb041a683b11c405e053e5b9
|
|
... to avoid extra debug output.
Change-Id: I04a0c7f6146af25bb34c73ec2bbe9e147ba9b864
|
|
git bisect run was not run from the git directory
Change-Id: Ic67b99dc1acef672c18f0fdf2ebdf07563966771
|
|
Change-Id: Iec22298d1655c2425c68c89487dce309b8638817
|
|
Change-Id: Ie1aecdb1fdbe7588a2619e301aa97dc25a5040b4
|
|
... to avoid cloning huge repos just to get a few files.
Change-Id: I8b6ec0a8ce3aa62ea09ebf1128016de748232d38
|
|
... before pushing new ones. This allows us to accurately match
history in base-artifacts to the data in the dashboard. Without
this we could have ghost reports in LNT dashboard for result entries
removed from base-artifacts.
Change-Id: Ifb1600f2650db28ccb8fb3d4643c120d4f746700
|
|
Since we enable building the docs in _build jobs without
maintainer-mode, we must remove the fake makeinfo wrapper in these
cases, otherwise we get build failures, for instance in
gcc/doc/iinstall.texi2html which expects that $DESTDIR/temp.html is
created by $MAKEINFO.
Change-Id: I67786b71ed8839d85d15805b4c4aa447b0f3aab0
|
|
threshold we can remove the workaround
Current consequence of this workaround:
=> num_symbol=0,
=> then, no hot symbols
=> then, no md5sum on hot symbols
=> then, no md5sum on the executable
=> then, no variability information, because it is on identical md5sum only
=> then, no bmk-specific-thresholds in LTO.
=> Then, no noise information for LTO config
What about removing this workaround
Change-Id: I9feb021bc8a89dcb684df3a0f22f9fd3ad29a270
|
|
.. that refer to git.linaro.org
Change-Id: Id5e13cc73a6ba71709de2915741ec3d0df46cd21
|
|
cpu information is specified in tcwg_bmk-config.sh:
- For jobs running on stm32 : cortex-m4
- For jobs running on tk1 : cortex-a15
- For fujitsu_speed jobs : a64fx
- For qc_speed jobs : cortex-x1
- For code_sve jobs : generic+sve
- .. All others (code_speed, code_size, code_vect) remains unspecified.
It is used when building the gnu toolchain in stage1 and stage2 using
abe option --set gcc_override_configure=--with-cpu=${rr[cpu]}
And it is to be used in benchmarking using cflags option -mcpu=${rr[cpu]}
Change-Id: I44d953f7e0376e7abddede42245cad55856d4fc0
|
|
Change-Id: I2f280df7bafc537ae628afbb7e7e184fa4da21e2
|
|
and keep them disabled in "check" jobs.
The rationale is that:
- we want to catch breakages when building the docs
- we still want to run the testsuite even if docs are broken
Change-Id: If3082d0e49e6cc3646f7038e38362223db24c2d3
|
|
previous commit about this was incomplete
Change-Id: Ia2d573082f2e1a8a6249a3f4fbc883b1f8aa7e1d
|
|
Change-Id: I7453e2c59153d349e44889b5fc9dfcce3d19c071
|
|
We now need patchwork token only to submit "checks", which is done
via glibc-cicd/check.py. This is initialized in pw-apply.sh, and
then used transparently in pw-report.sh. Therefore, only pw-apply.sh
needs to be passed "__pw_token TOKEN".
Change-Id: I512d680e771ac01777931a9c7e489e8fbff16b73
|
|
... which is useful for manual reproduction of pre-commit builds.
Change-Id: I0b66307ce2d0e0b86db293c5b25aec41e4dcc6e5
|
|
[: ==: unary operator expected
Change-Id: Ied457f5144fe28b0d20b1a7434430c551b08a553
|
|
dep_dir may not exist at this point
Change-Id: I7ef83cdd92314c2b6bf5c01a64b0c9a86270f0a8
|
|
new dashboard
In addition to the new cross_gcc and embed_gcc, this patch updates the
links for the other dashboards so that they point to the new ones,
which include only fail, flaky and total numbers.
Change-Id: I47754e2c9f06e0b33f9c9f56905f2d4a8ecd84e9
|
|
suffix where missing
A few configurations lacked soft/softfp/hard in their names.
Add it where missing, so that they are accepted: new jobs will be
created in Jenkins with the right names, and we'll delete the wrong
ones later, when we have enough history with the new ones.
Change-Id: Iab757da502dd406f2f672545b0afbc5ba381df0c
|
|
Change-Id: Ibef5db13a0215ed964ff830218728ec9bf9a19d4
|
|
Change-Id: Ib5cd982088ff7f3729c167f90fad28bfea775aba
|
|
Change-Id: If5a0d292e33600c052007275ead70f328f49c47d
|
|
Change-Id: I8f44fa78d4f3aa9cb7e1080ed371533b0642394e
|
|
This is important for WSL containers, for which we are using
a hard-coded ssh port number.
Change-Id: Ie0acb9bb00dbd6ee0a30ccf53c4ff84ca2e3827e
|
|
Bind-mount /run/WSL read-write so that /init can open and write
to sockets.
Change-Id: I3718f05d19ebe1100839f4ea60369662353228ec
|
|
Change-Id: Ic81fa981395d5936b2ed13db52ee64d85018f297
|
|
Change-Id: Ibab678121551af62fbf7a4361524df128e6a8be9
|
|
Change-Id: I4888abc38ca1dea107f8f1bf8a4ba7895345d3f4
|
|
Change-Id: I3c66aad6dcc29791aeaad0b87fab685952c21556
|
|
this function have been renamed into get_component_dir in a previous patch
Change-Id: Ieaae3790ba2bfe29e72d88eead91199988b249e8
|
|
be different than $current_project
Change-Id: Ifd4093b61eeb291474278e5354a6cf39e565f6b8
|
|
... so that history re-write can remove result entries that
no longer pass due to previously-removed flaky entries.
Change-Id: I83e826fb69d81bfff35887f2695723a17da48b8f
|
|
component in baseline
Change-Id: I6f0dc19570df5a82ac0661806e891ecded0a98ea
|
|
Change-Id: Ifef1b454fbfda72afc280e39015530bfeb252107
|
|
and re-generate LNT dashboard files.
Change-Id: I6bb1b814d2cd9d88faeda3dea7de853d23591af0
|
|
Change-Id: Ic4d03097ab214335f44cc736501cce73099fd431
|
|
... from validate_failures.py to the GNU testsuite dashboards.
Change-Id: I0b07cd0884f19ef4f3ee5f2aa95b29e1d65ca134
|
|
in jenkins-helper.sh for now as it will be used by chromium_build and bisect scripts
Change-Id: I249234f14b077e4ecfc771ea01812ab53dce73aa
|
|
After a recent change in validate_failures.py, the notification reports now include a few undesirable lines like:
# of stable fails 61
# of flaky entries 9
# of all tests 890731
which are irrelevant in the notification: we want to keep only the list of regressions.
This patch removes all lines after "Results Summary" (included).
Change-Id: I192d495161817e5faa6a63408cb2c323d193ff84
|
|
Change-Id: I8748e1d0a5440c09827c223379690fabc5dae0b9
|
|
Change-Id: I8c71b573ed0f7502c8156032aa07e03f031a0388
|