Commits · apertis/v2026dev2 · tests / ofono

Feb 18, 2025
- Bump to v2026dev2 · 017501ef
  Apertis CI authored 1 month ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  017501ef
Nov 19, 2024
- Bump to v2026dev1 · 63665835
  Apertis CI authored 4 months ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  63665835
Nov 18, 2024
- Bump to v2026dev0 · f5033e6f
  Apertis CI authored 4 months ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  f5033e6f
Nov 07, 2024
- Bump to v2025 · 76d6e0e7
  Walter Lozano authored 4 months ago
  
  Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
  76d6e0e7
Aug 16, 2024
- Fix helper-tools ref to v2025pre · bff348c1
  Walter Lozano authored 7 months ago
  
  Signed-off-by: Walter Lozano <walter.lozano@collabora.com>
  bff348c1
Aug 15, 2024
- Bump to v2025pre · f019d7f4
  Apertis CI authored 7 months ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  f019d7f4
May 28, 2024
- Target v2025dev3 · c4e2f559
  Apertis packagers authored 10 months ago
  
  Signed-off-by: Apertis packagers <packagers@lists.apertis.org>
  c4e2f559
Feb 19, 2024
- Target v2025dev2 · dacd80c4
  Apertis CI authored 1 year ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  dacd80c4
Nov 28, 2023
- Target v2025dev1 · 3a2f6c8f
  Apertis CI authored 1 year ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  3a2f6c8f
Nov 21, 2023
- Target v2025dev0 · 83456307
  Apertis CI authored 1 year ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  83456307
Nov 17, 2023
- Target v2024 · 46e2a7b3
  Apertis CI authored 1 year ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  46e2a7b3
Sep 04, 2023
- Target v2024pre · 14c15dcd
  Apertis CI authored 1 year ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  14c15dcd
Jun 30, 2023
- Target v2024dev3 · c9dde354
  Apertis CI authored 1 year ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  c9dde354
May 20, 2023

Binary update ofono 20230520 · 18b5695a

apertis-tests-apparmor-ofono_0.2023.2bv2024dev2b1_amd64.deb amd64/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2023.2bv2024dev2b1_amd64.deb amd64/lib/libofonod-malicious-override.so
apertis-tests-apparmor-ofono_0.2023.2bv2024dev2b1_armhf.deb armhf/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2023.2bv2024dev2b1_armhf.deb armhf/lib/libofonod-malicious-override.so
apertis-tests-apparmor-ofono_0.2023.2bv2024dev2b1_arm64.deb arm64/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2023.2bv2024dev2b1_arm64.deb arm64/lib/libofonod-malicious-override.so

Signed-off-by: Apertis Test Bot <testbot@apertis.org>

18b5695a

Feb 27, 2023
- Target v2024dev2 · 86db9e3e
  Apertis CI authored 2 years ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  86db9e3e
Jan 17, 2023
- Merge commit 'b1b1ded8 ' into wip/wlozano/apparmor-fixes · 43d69ec8
  Walter Lozano authored 2 years ago
  
  43d69ec8
Jan 16, 2023

Better fixing of cursor use · b1b1ded8

Walter Lozano authored 2 years ago

In commit 2e59623a a fix to the cursor use was introduced. However, the fix
tries to overcome the issue in a wrong way.

The problem is caused by the fact that the cursor is saved before running the
test and then it is used to check newer entries of a specific type (audit).
Since when journalctl is used with -t the cursor is first moved to the first
entry of the specific type the --after-cursor was changed for --cursor to
make the test pass.

However, a better approach would be to save the cursor also taking into
account the type of entry we are interested on, so later when we use it we
can safetly check entries with --after-crusor.

The only tricky case would be if there are no previous entries of the
specific case, which will lead to an empty cursor. So also handle that case.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

b1b1ded8

Jan 06, 2023

Merge commit '2e59623a' into wip/wlozano/cursor · d9bf1e6c
Walter Lozano authored 2 years ago
```
Merge latest common changes to fix the use of journalctl cursor.
```
d9bf1e6c

Fix journalctl cursor use · 2e59623a

Walter Lozano authored 2 years ago

Using --after-cursor in combination with -t audit does produces the expected
output since the filtering logic is applied before and after that the cursor
is moved to next valid entry. In this case, using --after-cursor will cause
the output to miss the first entry in the log.

Fix the issue by using --cursor instead.

Signed-off-by: Walter Lozano <walter.lozano@collabora.com>

2e59623a

Dec 05, 2022
- Target v2024dev1 · 5018fc98
  Apertis CI authored 2 years ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  5018fc98
Nov 30, 2022
- Target v2024dev0 · c6210796
  Apertis CI authored 2 years ago
  
  Signed-off-by: Apertis CI <devel@lists.apertis.org>
  Unverified
  
  c6210796
Nov 16, 2022
- Add 'common/' from commit '82a22234 ' · a8a44509
  Detlev Casanova authored 2 years ago
  
  git-subtree-dir: common git-subtree-mainline: 3635a9eb git-subtree-split: 82a22234
  a8a44509
- common: Remove common folder · 3635a9eb
  Detlev Casanova authored 2 years ago
  
  It will be replaced by a git subtree to point to the common repository
  3635a9eb
Oct 12, 2022

run-aa-test: Avoid reading previous tests log · 82a22234

Detlev Casanova authored 2 years ago


To read the log for the currently running test only, the current
date and time is used with the `--since` argument of
journalctl.

Sometimes, tests can run too fast one after the other and the last log
entries of the previous test is at the same timestamp as the one
running.

That makes the current test parse log entries from the
previous test, which is unexpected, and the test fails.

Unfortunately, the `--since` argument of journalctl doesn't allow for
more precision than the second.

To fix that, use the current journal cursor instead of time.
With this approach, no entries from the previous test is read by the
current test

Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>

82a22234

Aug 15, 2022
- Update release to v2023dev3 · d9ab1314
  Ritesh Raj Sarraf authored 2 years ago
  
  Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
  Unverified
  
  d9ab1314
Dec 15, 2021
- Target v2023dev1 · 824efecb
  Ritesh Raj Sarraf authored 3 years ago
  
  Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>
  Unverified
  
  824efecb
Dec 09, 2021

Bind mount malicious library to test unauthorized access · 167e6d94

Frederic Danis authored 3 years ago

Bind mount the malicious library in a place accessible by the loader and
not blocked by AppArmor, i.e. in place of an existing library, allowing
test that AppArmor will block the malicious behavior.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

167e6d94

Merge commit '3e4dea3e ' into apertis/v2023dev0 · a99b5981
Frederic Danis authored 3 years ago

a99b5981

Dec 08, 2021

Add architecture specific library name · 3e4dea3e

Frederic Danis authored 3 years ago


This will allow to create the architecture library path like
`/usr/lib/arm-linux-gnueabihf/`.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

3e4dea3e

Fix tmp dirs removal · 7b8c353e
Frederic Danis authored 3 years ago
```
Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>
```
7b8c353e

Dec 03, 2021

common-subtree: Fix branch to use · 77261179

Frederic Danis authored 3 years ago and

Emanuele Aina committed 3 years ago


The `test/common` repository uses `apertis/v20*` branches, not `main` or
`master`.
`common-subtree.sh` is using the current branch from the working
test repo to infer which remote branch to import: if it's not in the
`apertis/*` form, retrieve the latest branch from the `test/common`
repository.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

77261179

Nov 15, 2021
- Target v2023dev0 · f469505f
  Ritesh Raj Sarraf authored 3 years ago
  
  Signed-off-by: Ritesh Raj Sarraf <rrs@debian.org>
  Unverified
  
  f469505f
Oct 13, 2021

update-test-path: Fix LD_LIBRARY_PATH setup · 0e868dac

Frederic Danis authored 3 years ago


This script fails when LD_LIBRARY_PATH is not set before calling it and
calling script has `nounset` option set.

Signed-off-by: Frédéric Danis <frederic.danis@collabora.com>

0e868dac

Sep 20, 2021
- Fix release string to v2022pre · 851a2dea
  Ritesh Raj Sarraf authored 3 years ago
  
  Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
  Unverified
  
  851a2dea
Sep 17, 2021

Binary update ofono 20210917 · c71b68da

Apertis Test Bot authored 3 years ago

apertis-tests-apparmor-ofono_0.2021.6bv2022dev3b1_amd64.deb amd64/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2021.6bv2022dev3b1_amd64.deb amd64/lib/libofonod-malicious-override.so
apertis-tests-apparmor-ofono_0.2021.6bv2022dev3b1_armhf.deb armhf/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2021.6bv2022dev3b1_armhf.deb armhf/lib/libofonod-malicious-override.so
apertis-tests-apparmor-ofono_0.2021.6bv2022dev3b1_arm64.deb arm64/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2021.6bv2022dev3b1_arm64.deb arm64/lib/libofonod-malicious-override.so

Signed-off-by: Apertis Test Bot <testbot@apertis.org>

c71b68da

Sep 15, 2021

Binary update ofono 20210915 · 4b2d74d6

Apertis Test Bot authored 3 years ago

apertis-tests-apparmor-ofono_0.2021.2bv2021.0b3_amd64.deb amd64/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2021.2bv2021.0b3_amd64.deb amd64/lib/libofonod-malicious-override.so
apertis-tests-apparmor-ofono_0.2021.2bv2021.0b3_armhf.deb armhf/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2021.2bv2021.0b3_armhf.deb armhf/lib/libofonod-malicious-override.so
apertis-tests-apparmor-ofono_0.2021.2bv2021.0b3_arm64.deb arm64/lib/libofonod-malicious-override.so.0
apertis-tests-apparmor-ofono_0.2021.2bv2021.0b3_arm64.deb arm64/lib/libofonod-malicious-override.so

Signed-off-by: Apertis Test Bot <testbot@apertis.org>

4b2d74d6