| Message ID | 20191018205338.14879-10-trini@konsulko.com |
|---|---|
| State | Changes Requested |
| Delegated to: | Tom Rini |
| Headers | show |
| Series | Moving test/py to Python 3 | expand |
On 10/18/19 2:53 PM, Tom Rini wrote:
> Currently, these tests are skipped when run in CI.
How? If they're being skipped by some other mechanism, do we need to
remove that other mechanism now that we're actively specifying "not fs"
when running under CI?
On Fri, Oct 18, 2019 at 03:16:45PM -0600, Stephen Warren wrote: > On 10/18/19 2:53 PM, Tom Rini wrote: > > Currently, these tests are skipped when run in CI. > > How? If they're being skipped by some other mechanism, do we need to remove > that other mechanism now that we're actively specifying "not fs" when > running under CI? Currently they get auto-skipped. Thinking harder, I bet it's related to patch 2 where I un-break PATH and now we're finding tools in /sbin and try and run the tests.
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index a46ab5487257..2528a5a9a2e4 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -177,6 +177,7 @@ sandbox test.py: variables: TEST_PY_BD: "sandbox" BUILDMAN: "^sandbox$" + TEST_PY_TEST_SPEC: "not fs" <<: *buildman_and_testpy_dfn sandbox_spl test.py: @@ -200,6 +201,7 @@ sandbox_flattree test.py: variables: TEST_PY_BD: "sandbox_flattree" BUILDMAN: "^sandbox_flattree$" + TEST_PY_TEST_SPEC: "not fs" <<: *buildman_and_testpy_dfn vexpress_ca15_tc2 test.py:
Currently, these tests are skipped when run in CI. With the move to python3 and a newer host they are being run, but showing failures that need more investigation. For now, skip these tests as we had been doing. Signed-off-by: Tom Rini <trini@konsulko.com> --- .gitlab-ci.yml | 2 ++ 1 file changed, 2 insertions(+)