From: ROCKTAKEY <rocktakey@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 62472-done@debbugs.gnu.org
Subject: [bug#62472] [PATCH 0/2] gnu: conan: Remove some failed tests
Date: Sat, 1 Apr 2023 01:57:53 +0900 [thread overview]
Message-ID: <bd34cf0b-e823-89aa-8c27-1fa6ba6fd8bf@gmail.com> (raw)
In-Reply-To: <87pm8pvvql.fsf@gmail.com>
It works well. Thanks!
On 2023/03/31 23:30, Maxim Cournoyer wrote:
> Hello,
>
> ROCKTAKEY <rocktakey@gmail.com> writes:
>
>> Hi!
>>
>> Thanks for your work. Updating to 2.0.2 is better.
>>
>> But in my environment, some other tests are failed:
>>
>> =========================== short test summary info
>> ============================
>> FAILED
>> conans/test/functional/toolchains/cmake/test_cmake.py::LinuxTest::test_toolchain_linux_0_Debug
>> FAILED
>> conans/test/integration/command_v2/list_test.py::TestListPrefs::test_list_pkg_ids[True]
>> FAILED
>> conans/test/integration/command_v2/list_test.py::TestListPrefs::test_list_pkg_ids_all_rrevs[True]
>> FAILED
>> conans/test/integration/command_v2/list_test.py::TestListPrefs::test_list_latest_prevs[True]
>> FAILED
>> conans/test/integration/command_v2/list_test.py::TestListPrefs::test_list_all_prevs[True]
>> = 5 failed, 3016 passed, 321 skipped, 165 xfailed, 9 xpassed, 12
>> warnings in 510.98s (0:08:30) =
> I was able to reproduce it for test_toolchain_linux_0_Debug, which I've
> now skipped, but not for the other tests. The build farm reproduced
> them though [0]:
>
> =========================== short test summary info ============================
> FAILED conans/test/functional/toolchains/cmake/test_cmake.py::LinuxTest::test_toolchain_linux_0_Debug
> FAILED conans/test/integration/command_v2/list_test.py::TestListPrefs::test_list_pkg_ids[True]
> FAILED conans/test/integration/command_v2/list_test.py::TestListPrefs::test_list_pkg_ids_all_rrevs[True]
> FAILED conans/test/integration/command_v2/list_test.py::TestListPrefs::test_list_latest_prevs[True]
> FAILED conans/test/integration/command_v2/list_test.py::TestListPrefs::test_list_all_prevs[True]
>
> [0] https://ci.guix.gnu.org/build/666884/log/raw
>
> I've reported the failure upstream and disabled these as well:
>
> --8<---------------cut here---------------start------------->8---
> modified gnu/packages/package-management.scm
> @@ -1209,7 +1209,7 @@ (define system #$(or (%current-target-system)
> (setenv "CONFIG_SHELL" (which "sh"))
> (setenv "PATH" (string-append (getenv "PATH") ":"
> #$output "/bin"))
> - (invoke "python" "-m" "pytest"
> + (invoke "python" "-m" "pytest" "-vv"
> "-n" (number->string (parallel-job-count))
> "-m" "not slow"
> ;; Disable problematic tests.
> @@ -1222,6 +1222,12 @@ (define system #$(or (%current-target-system)
> ;; expected by the following test.
> "and not pkg_config_path "
> "and not compare " ;caused by newer node-semver?
> + ;; This test hard-codes a compiler version.
> + "and not test_toolchain "
> + ;; The 'test_list' tests may fail
> + ;; non-deterministically (see:
> + ;; https://github.com/conan-io/conan/issues/13583).
> + "and not test_list "
> ;; These tests fail when Autoconf attempt to load a
> ;; shared library in the same directory (see:
> ;; https://github.com/conan-io/conan/issues/13577).
> --8<---------------cut here---------------end--------------->8---
>
> Hopefully it now builds on your side as well. Thanks for the report!
>
prev parent reply other threads:[~2023-03-31 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-26 19:13 [bug#62472] [PATCH 0/2] gnu: conan: Remove some failed tests ROCKTAKEY
2023-03-27 8:18 ` [bug#62472] [PATCH 1/2] gnu: conan: Remove some tests about git submodule ROCKTAKEY
2023-03-27 8:18 ` [bug#62472] [PATCH 2/2] gnu: conan: Remove test_token_expired test ROCKTAKEY
2023-03-30 20:13 ` bug#62472: [PATCH 0/2] gnu: conan: Remove some failed tests Maxim Cournoyer
2023-03-31 10:25 ` [bug#62472] " ROCKTAKEY
2023-03-31 14:30 ` Maxim Cournoyer
2023-03-31 16:57 ` ROCKTAKEY [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bd34cf0b-e823-89aa-8c27-1fa6ba6fd8bf@gmail.com \
--to=rocktakey@gmail.com \
--cc=62472-done@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.