autopkgtests should be run in -ci jobs
Bug #1334141 reported by
Michi Henning
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu CI Services |
New
|
Undecided
|
Unassigned | ||
| unity-scopes-api |
Fix Released
|
Medium
|
Michi Henning | ||
Bug Description
We need a way to run Jussi's recent autopkg test from Jenkins, as well as locally. Otherwise, we will forget to run the test, and it'll go stale on us over time because it'll gradually drop off people's memory.
Checking that the autopkg stuff still works locally needs to be easy: ideally, a cmake target. If that isn't doable, a python script or some such, so we don't have to spend ages setting up a chroot and the like by hand.
Related branches
lp:~michihenning/unity-scopes-api/scope-cache-dir
- Michal Hruby (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Jamie Strandboge: Approve
-
Diff: 2237 lines (+609/-346)60 files modifiedCONFIGFILES (+1/-1)
HACKING (+14/-9)
RELEASE_NOTES.md (+15/-0)
debian/changelog (+5/-2)
debian/libunity-scopes2.symbols (+14/-6)
debian/tests/scopebuild (+5/-54)
debian/tests/scopetest.cpp (+62/-0)
demo/click/scope-click/scope-click.cpp (+1/-1)
demo/scopes/scope-A/scope-A.cpp (+1/-1)
demo/scopes/scope-B/scope-B.cpp (+4/-4)
demo/scopes/scope-C/scope-C.cpp (+1/-1)
demo/scopes/scope-D/scope-D.cpp (+1/-1)
demo/scopes/scope-N/scope-N.cpp (+1/-1)
demo/scopes/scope-S/scope-S.cpp (+1/-1)
doc/tutorial.dox (+3/-3)
include/unity/scopes/AbstractScopeBase.h (+65/-0)
include/unity/scopes/ScopeBase.h (+56/-29)
include/unity/scopes/internal/DfltConfig.h.in (+1/-0)
include/unity/scopes/internal/RuntimeImpl.h (+1/-0)
include/unity/scopes/internal/ScopeBaseImpl.h (+21/-3)
include/unity/scopes/internal/ScopeConfig.h (+12/-12)
include/unity/scopes/internal/ScopeLoader.h (+3/-11)
include/unity/scopes/testing/TypedScopeFixture.h (+6/-6)
scoperegistry/scoperegistry.cpp (+27/-19)
scoperunner/scoperunner.cpp (+20/-43)
smartscopesproxy/smartscopesproxy.cpp (+3/-2)
src/scopes/ScopeBase.cpp (+12/-1)
src/scopes/internal/RegistryConfig.cpp (+1/-1)
src/scopes/internal/RuntimeConfig.cpp (+1/-1)
src/scopes/internal/RuntimeImpl.cpp (+66/-23)
src/scopes/internal/ScopeBaseImpl.cpp (+67/-1)
src/scopes/internal/ScopeConfig.cpp (+7/-7)
src/scopes/internal/ScopeLoader.cpp (+4/-35)
src/scopes/internal/zmq_middleware/ZmqConfig.cpp (+1/-1)
test/CMakeLists.txt (+1/-0)
test/autopkg/CMakeLists.txt (+4/-0)
test/gtest/scopes/Activation/TestScope.h (+1/-1)
test/gtest/scopes/IdleShutdown/SlowSearchScope.cpp (+1/-1)
test/gtest/scopes/IdleShutdown/SlowSearchScope.h (+1/-1)
test/gtest/scopes/Registry/scopes/testscopeA/testscopeA.cpp (+1/-1)
test/gtest/scopes/Registry/scopes/testscopeB/testscopeB.cpp (+1/-1)
test/gtest/scopes/Runtime/PusherScope.h (+5/-6)
test/gtest/scopes/Runtime/SlowCreateScope.h (+5/-6)
test/gtest/scopes/ScopeBase/ScopeBase_test.cpp (+1/-1)
test/gtest/scopes/ScopeBase/scopelib.cpp (+1/-1)
test/gtest/scopes/internal/ScopeConfig/ScopeConfig_test.cpp (+1/-1)
test/gtest/scopes/internal/ScopeConfig/complete_config.ini.in (+1/-0)
test/gtest/scopes/internal/ScopeLoader/MyScope.h (+1/-1)
test/gtest/scopes/internal/ScopeLoader/ScopeA.cpp (+1/-1)
test/gtest/scopes/internal/ScopeLoader/ScopeB.cpp (+1/-1)
test/gtest/scopes/internal/ScopeLoader/ScopeLoader_test.cpp (+20/-26)
test/gtest/scopes/internal/ScopeLoader/ThrowUnityExFromStart.cpp (+1/-1)
test/gtest/scopes/internal/ScopeLoader/ThrowUnknownExFromStart.cpp (+1/-1)
test/gtest/scopes/testing/IsolatedScope/scope.cpp (+32/-5)
test/gtest/scopes/testing/IsolatedScope/scope.h (+15/-3)
test/gtest/scopes/testing/IsolatedScopeBenchmark/IsolatedScopeBenchmark_test.cpp (+1/-1)
test/gtest/scopes/testing/IsolatedScopeBenchmark/scope.cpp (+1/-1)
test/gtest/scopes/testing/IsolatedScopeBenchmark/scope.h (+1/-1)
test/headers/CMakeLists.txt (+6/-3)
test/headers/check_public_headers.py (+1/-1)
| Changed in unity-scopes-api: | |
| importance: | Undecided → Medium |
Revision history for this message
| Michał Sawicz (saviq) wrote | #1 |
| summary: |
- Need a test for autopkg test + autopkgtests should be run in -ci jobs |
Revision history for this message
| Michał Sawicz (saviq) wrote | #2 |
Revision history for this message
| Michi Henning (michihenning) wrote | #3 |
| Changed in unity-scopes-api: | |
| assignee: | nobody → Michi Henning (michihenning) |
| status: | New → In Progress |
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #4 |
| Changed in unity-scopes-api: | |
| status: | In Progress → Fix Committed |
| Changed in unity-scopes-api: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
FWIW it is being run in proposed already:
http://
Those get triggered whenever the package in question, or any of its dependencies, get updated in proposed (ubuntu proposed, not devel-proposed image).
AFAIK the long-term plan is to transition all non-make-check (e.g. autopilot, qml UI tests) to autopkgtests, meaning there's a standard way to execute them (DEP-8) locally or remotely.
The first thing that should happen, IMO, is they should be run in -ci jobs for packages that ship them, hence the ubuntu-